From: Greg KH <greg@kroah.com>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: linux-kernel@vger.kernel.org, stable@vger.kernel.org
Subject: Re: Latest kernel stable/longterm status
Date: Wed, 11 Jan 2012 07:13:05 -0800 [thread overview]
Message-ID: <20120111151305.GC24077@kroah.com> (raw)
In-Reply-To: <CAMuHMdVSQS0B_DotQytbmeBs0=a4=8NMhdG5UVXbWjBXYrykFQ@mail.gmail.com>
On Wed, Jan 11, 2012 at 01:42:08PM +0100, Geert Uytterhoeven wrote:
> On Wed, Jan 11, 2012 at 13:32, Geert Uytterhoeven <geert@linux-m68k.org> wrote:
> > On Tue, Jan 10, 2012 at 01:37, Greg KH <greg@kroah.com> wrote:
> >> First off, please everyone remember to mark any patch that you want to
> >> have applied to the stable kernel trees with a simple:
> >> Cc: stable <stable@vger.kernel.org>
> >> marking in the Signed-off-by: area. Once the patch hits Linus's tree, I
> >> will automatically be notified of it and it will be applied if possible.
> >> If it does not applied, you will be notified of that.
> >
> > How do you want us to specify to which versions it should be applied?
>
> Cc: v3.2, v3.1, ... <stable@vger.kernel.org>
That can work, or if you read Documenation/stable_kernel_rules.txt you
can see some other ways to nicely do this :)
thanks,
greg k-h
prev parent reply other threads:[~2012-01-11 15:14 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-10 0:37 Greg KH
2012-01-10 2:26 ` Steven Rostedt
2012-01-10 10:03 ` Tim Gardner
2012-01-10 23:56 ` Greg KH
2012-01-11 1:38 ` Anca Emanuel
2012-01-11 10:10 ` Tim Gardner
2012-01-11 15:12 ` Greg KH
2012-01-11 20:37 ` Tim Gardner
2012-01-11 20:52 ` Greg KH
2012-01-21 13:36 ` Willy Tarreau
2012-01-21 13:47 ` Greg KH
2012-01-21 14:45 ` Willy Tarreau
2012-01-11 12:32 ` Geert Uytterhoeven
2012-01-11 12:42 ` Geert Uytterhoeven
2012-01-11 15:13 ` Greg KH [this message]
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=20120111151305.GC24077@kroah.com \
--to=greg@kroah.com \
--cc=geert@linux-m68k.org \
--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
Powered by JetHome