From: Stanislaw Gruszka <sgruszka@redhat.com>
To: Greg KH <greg@kroah.com>
Cc: stable@kernel.org, linux-kernel@vger.kernel.org
Subject: -longterm kernels (Was: Re: [stable] Patch Upstream: iwlwifi: fix skb usage after free)
Date: Thu, 5 May 2011 16:58:55 +0200 [thread overview]
Message-ID: <20110505145854.GA4670@redhat.com> (raw)
In-Reply-To: <20110504223605.GA5967@kroah.com>
(Removing Cc as probably not interested, adding LKML)
On Wed, May 04, 2011 at 03:36:05PM -0700, Greg KH wrote:
> > Cc: stable@kernel.org # 2.6.32+
>
> This doesn't apply to the .32 or .33-stable kernels. If you wish to see
> it there, can someone please provide a backport and send it to
> stable@kernel.org ?
Done.
BTW, Greg, perhaps -logterm releasing policy should be revised somehow.
Currently we have .32, .33, .34, .35 -longterm, what is kind a much. If
I could suggest something, would be nice to have longterm chosen
versions predictable and constants i.e. one from every 3 kernel
releases, like .35, .38, .41 ... . That would make distributions, that
try to do release every half year very happy, because they will know
what kernel to choose, which will be widely supported and tested. Also
developers will have a bit less work with backporting fixes, as having
same bug in n and n-3 release is less probable, than having the same bug
in n and n-1.
Stanislaw
next parent reply other threads:[~2011-05-05 14:58 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <201105030110.p431A5W0005426@hera.kernel.org>
[not found] ` <20110504223605.GA5967@kroah.com>
2011-05-05 14:58 ` Stanislaw Gruszka [this message]
2011-05-05 15:17 ` [stable] -longterm kernels (Was: Re: Patch Upstream: iwlwifi: fix skb usage after free) Willy Tarreau
2011-05-05 15:25 ` -longterm kernels (Was: Re: [stable] " Greg KH
2011-05-07 14:55 ` -longterm kernels Stanislaw Gruszka
2011-05-07 15:40 ` Greg KH
2011-05-07 15:57 ` Stanislaw Gruszka
2011-05-07 19:01 ` Greg KH
2011-05-09 9:18 ` Stanislaw Gruszka
2011-05-08 5:09 ` Mike Galbraith
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=20110505145854.GA4670@redhat.com \
--to=sgruszka@redhat.com \
--cc=greg@kroah.com \
--cc=linux-kernel@vger.kernel.org \
--cc=stable@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