LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: Ingo Molnar <mingo@elte.hu>
Cc: Andrew Morton <akpm@linux-foundation.org>,
	tglx@linutronix.de, torvalds@linux-foundation.org,
	linux-kernel@vger.kernel.org, roland@redhat.com,
	stable@kernel.org
Subject: Re: [stable] [PATCH] x86_64 ia32 syscall restart fix
Date: Fri, 29 Feb 2008 21:48:15 -0800	[thread overview]
Message-ID: <20080301054815.GA20032@kroah.com> (raw)
In-Reply-To: <20080229212014.GJ27212@elte.hu>

On Fri, Feb 29, 2008 at 10:20:14PM +0100, Ingo Molnar wrote:
> 
> * Andrew Morton <akpm@linux-foundation.org> wrote:
> 
> > I believe the -stable guys have a bot which trolls the mainline 
> > commits mailing list for "cc:.*stable@kernel.org".  So anybody 
> > anywhere in the patch delivery chain can append "Cc: 
> > <stable@kernel.org>" and things should get appropriate consideration.
> 
> ok, didnt know about that.

Yes, it's quite handy, so just add that to your patch and we
automatically grab it.

I've added that info to the stable rules file in Documentation, should I
"announce" it anywhere else?

> > The place where I suspect there is a lot of lossage is people simply 
> > not thinking about whether a fix should be backported.  I'm forever 
> > fussing about that for the patches I handle (and I still miss some) 
> > but I have a suspicion that not all tree-owners do this fully.
> 
> we watch out for this, but still, about 50% of the cases, the 
> realization "this should be backported" comes later on. Often because 
> fixes get applied with low latency, and testers lag in realizing that 
> some particular -stable problem is fixed by a -git fix. Sometimes people 
> do bisection in search of backportable fixes - that too has a lag.
> 
> so the more formal:
> 
>     Backport-suggested-by: commit-id, person

I normally just add the person who suggested the patch to be added to
the Cc: if they are not already on the signed-off-by: list.

Does it really matter who suggested that -stable pick it up?

> 
> entry would solve both cases. Also, a commit entry in -stable:
> 
>     Backported-from: commit-id

We already add that info to the commit, but not necessarily in a
"standard" format.  If you want it in something like this, it's trivial
to provide it.

thanks,

greg k-h

  reply	other threads:[~2008-03-01  5:54 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-29  3:57 Roland McGrath
2008-02-29 15:52 ` Ingo Molnar
2008-02-29 16:26   ` Linus Torvalds
2008-02-29 16:45     ` Ingo Molnar
2008-02-29 17:03       ` Linus Torvalds
2008-02-29 17:17         ` Ingo Molnar
2008-02-29 17:37           ` Ingo Molnar
2008-02-29 21:02             ` Andrew Morton
2008-02-29 21:20               ` Ingo Molnar
2008-03-01  5:48                 ` Greg KH [this message]
2008-02-29 22:42     ` Roland McGrath
2008-02-29 23:18       ` Linus Torvalds
2008-03-07 22:56 ` [PATCH] x86_64 ptrace orig_ax on ia32 task Roland McGrath
2008-03-07 23:18   ` Linus Torvalds
2008-03-08  1:37     ` Roland McGrath
2008-03-10 19:19   ` Chuck Ebbert
2008-03-10 19:48     ` Linus Torvalds
2008-03-10 20:01       ` Roland McGrath
2008-03-11  9:32         ` Ingo Molnar

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=20080301054815.GA20032@kroah.com \
    --to=greg@kroah.com \
    --cc=akpm@linux-foundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=roland@redhat.com \
    --cc=stable@kernel.org \
    --cc=tglx@linutronix.de \
    --cc=torvalds@linux-foundation.org \
    --subject='Re: [stable] [PATCH] x86_64 ia32 syscall restart fix' \
    /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

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).