04:25 <DC-IRC> [Discord] <leap1234567890> This isn't really related to Armbian, though I would like to ask a question

04:26 <DC-IRC> [Discord] <leap1234567890> I've been porting postmarketOS to RK322X SoCs, which utilizes patches from Armbian and LibreELEC

04:28 <DC-IRC> [Discord] <leap1234567890> The pull request have been merged though I still need permission from LibreELEC and Armbian to use the patches

04:29 <DC-IRC> [Discord] <leap1234567890> I originally wanted to go to LibreELEC though they seem to only have IRC, which I don't like to use

04:30 <DC-IRC> [Discord] <leap1234567890> I originally wanted to go to LibreELEC because the patches were taken from there though they seem to only have IRC for support (besides the forum), which I don't like to use

04:31 <DC-IRC> [Discord] <leap1234567890> So I went to this server instead

04:31 <DC-IRC> [Discord] <leap1234567890> https://gitlab.postmarketos.org/postmarketOS/pmaports/-/merge_requests/6982

04:31 <DC-IRC> [Discord] <leap1234567890> Here's the pull request I'm talking about

04:39 <DC-IRC> [Discord] <Werner> Check the GPL 2.0 license for what you are allowed to do under which conditions and what not.

04:41 <DC-IRC> [Discord] <leap1234567890> This is about patches. I understand that it uses GPL 2.0 though I don't know if they apply to the patches.

04:42 <DC-IRC> [Discord] <leap1234567890> The kernel packages in postmarketOS doesn't seem to specify licenses on the patches

04:49 <chewitt> the "pmaports" repo that you are adding patch files to is GPLv3 https://gitlab.postmarketos.org/postmarketOS/pmaports/-/blob/master/LICENSE

04:50 <chewitt> this applies to the repository itself, i.e. the packaging mechanism

04:51 <chewitt> the kernel is GPLv2 (only) and the patches are either modifying existing GPLv2 code or adding new (marked as GPLv2) code

04:51 <chewitt> again, nothing unusual, nothing complicated, and nothing that needs permission to use

04:52 <chewitt> as per comment in #libreelec channel, if you are adding new patches of your own, create diff patches with subject/description and visible author

04:52 <chewitt> so that when someone else borrows them later the attribution can be respected

04:53 <chewitt> and we perhaps know who to ask Q's to if/when something doesn't work

04:53 <chewitt> if changes are simple, e.g. device tree things that add missing nodes; upstream them to the kernel

04:54 <chewitt> there's a few simple rules to follow, and lots of people around who can coach the process if you need help

04:57 <DC-IRC> [Discord] <leap1234567890> ah

04:59 <DC-IRC> [Discord] <leap1234567890> a reviewer said something about the signed-of-by field on patches

04:59 <DC-IRC> [Discord] <leap1234567890> i don't know what to do since some of the patches doesn't have them

07:25 <DC-IRC> [Discord] <gin_kage> My point was that, as it's not compatible with every board, it made little sense to use exactly the same flash module form-factor with exactly the same connectors.

07:28 <DC-IRC> [Discord] <mecoblock> Yeah that I get but idk how else you’d keep backwards compatibility to emmc on those newer boards