On Wed, Feb 17, 2021 at 9:30 AM Bastien Nocera <hadess@xxxxxxxxxx> wrote: > > On Fri, 2021-02-12 at 14:07 +0100, Bastien Nocera wrote: > > On Thu, 2021-02-11 at 17:23 -0600, Justin Forbes wrote: > > > On Thu, Feb 11, 2021 at 1:01 PM Bastien Nocera <hadess@xxxxxxxxxx> > > > wrote: > > > > > > > > On Thu, 2021-02-11 at 19:32 +0100, Hans de Goede wrote: > > > > <snip> > > > > > So where do I submit these once backported ? Do I just add > > > > > them > > > > > to > > > > > dist-git > > > > > as before ? AFAIK 5.11 will be the first kernel-ark based > > > > > Fedora > > > > > kernel > > > > > (at least 5.10 dist-git does not look ark based), right ? > > > > > > > > I recently wanted to do that for a Bluetooth patch, and this is > > > > how > > > > I > > > > went about it, along with discussions that happened on the list: > > > > https://gitlab.com/cki-project/kernel-ark/-/merge_requests/872 > > > > > > > > I don't know whether I would have needed to proceed to get this > > > > particular patch into stable releases, like Fedora 33 though. > > > > > > > > > > The Fedora stable branches are a bit different, in that they do not > > > copy over to ELN, so it is a much less formal process. Basically > > > either I take it or I don't. And that is typically determined by a) > > > What is the upstream status? b) How invasive is the backport? c) > > > What > > > is it trying to solve? > > > > Coming back to the merge request I filed, I think that all 3 of those > > questions are answered. > > > > Do I need to do anything else? A separate merge request? > > Justin, can you please explain what's needed to land upstream patches > into stable versions of Fedora, with the above patch as an example? > > The merge request I filed against what will be the rawhide kernel has > all the 3 bits of information you requested. Is something missing? > > How do we need to contribute the upstream changes to make it as easy as > possible for you, so those patches get into stable kernels quickly? > Sorry, this should have been cleared up and sent out by now, but I am in TX and have had very little power this week, so I haven't gotten things pushed out. At some point this week, there will be a fedora-5.11 branch in the kernel-ark repository which is where changes for 5.11 across all stable Fedora releases will go. From a process standpoint, it will work similar to kernel-ark in that you just open up a merge request, but being that it is a Fedora specific branch, it won't need to wait for acks, etc. For 5.10 stable updates until we rebase to 5.11, the process is generally sending an email to this list and I will pull it in before I do the next build. Justin _______________________________________________ kernel mailing list -- kernel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to kernel-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/kernel@xxxxxxxxxxxxxxxxxxxxxxx Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
