stable.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: dsterba@suse.cz, stable@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: Stable patches that don't apply to older kernels and how to get them
Date: Thu, 21 Mar 2019 18:31:56 +0100	[thread overview]
Message-ID: <20190321173156.GA4171@kroah.com> (raw)
In-Reply-To: <20190321163941.GA11121@kroah.com>

On Thu, Mar 21, 2019 at 05:39:41PM +0100, Greg KH wrote:
> On Thu, Mar 21, 2019 at 04:14:14PM +0100, David Sterba wrote:
> > Hi,
> > 
> > would it be possible to have a git repository with all patches that are
> > submitted to stable@ but don't apply directly?
> > 
> > I get notified by mail, that's fine though it's not that convenient to
> > see all the pending patches for backport to a given version.
> > 
> > My proposal:
> > 
> > - create a separate stable-unapplied git repository
> > 
> > - if a patch does not apply to a given version, it's stored as-is to a
> >   directory of the base version (like 4.4)
> > 
> > - once a fixed version is applied to stable-queue.git/released-4.4, the
> >   patch in the other repo is deleted
> > 
> > I believe this can be highly automated and once implemented would not
> > too much additional work to the stable workflow. I could possibly write
> > a scraper of the mail archives to pick the patches and manage the
> > repository but I think that a central repository could help other
> > maintainers too or to spread the load to all interested developers.
> > 
> > If something like that already exists, please let me know.
> 
> Nothing like this exists, sorry.
> 
> And if you want to automate this, wonderful, but I do not have any time
> to do so, and it does not fit into my workflow at all.  Patches that do
> not apply are the exception by far, not the rule, so I doubt this would
> really help out much.
> 
> And of course, the i915 developers would just ignore it, as they hold
> the record for patches that never apply, and then never send patches in
> as they are already 6-8 months ahead :)

Note, what does work today is Sasha's bot that finds patches that are
 cc: stable and tries to apply them to older kernels and sends you an
email if the patch fails.  That is running today in semi-frequent waves,
and we have gotten backports sent to the list before the patch lands in
Linus's tree, which is great.  So you can take advantage of this now if
you want to.

thanks,

greg k-h

  reply	other threads:[~2019-03-21 17:32 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-03-21 15:14 Stable patches that don't apply to older kernels and how to get them David Sterba
2019-03-21 16:39 ` Greg KH
2019-03-21 17:31   ` Greg KH [this message]
2019-03-21 18:19   ` David Sterba
2019-03-21 18:30     ` Greg KH

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20190321173156.GA4171@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=dsterba@suse.cz \
    --cc=linux-kernel@vger.kernel.org \
    --cc=stable@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).