From: "Pasi Kärkkäinen" <pasik@iki.fi>
To: Ben Hutchings <ben@decadent.org.uk>
Cc: Greg KH <greg@kroah.com>, Tim Bird <tbird20d@gmail.com>,
linux-kernel@vger.kernel.org, stable-review@kernel.org,
tim.bird@am.sony.com, akpm@linux-foundation.org,
torvalds@linux-foundation.org, stable@kernel.org,
alan@lxorguk.ukuu.org.uk
Subject: Re: [Stable-review] Future of the -longterm kernel releases (i.e. how we pick them).
Date: Thu, 18 Aug 2011 14:28:06 +0300 [thread overview]
Message-ID: <20110818112806.GF32373@reaktio.net> (raw)
In-Reply-To: <1313627614.2799.61.camel@deadeye>
On Thu, Aug 18, 2011 at 01:33:34AM +0100, Ben Hutchings wrote:
> On Tue, 2011-08-16 at 21:58 -0700, Greg KH wrote:
> > On Tue, Aug 16, 2011 at 04:01:57PM -0700, Tim Bird wrote:
> [...]
> > > One specific issue I have is support for PREEMPT_RT, so that's a big
> > > factor in selecting Sony kernel versions. Thus, coordinating with the
> > > RT patchset kernel versions is important to me. Currently
> > > that would mean 3.0 is a good candidate.
> >
> > 3.0 is looking like a good candidate, but we haven't seen 3.1 yet :)
> [...]
>
> I'm quite happy with 3.0 in terms of stability and features, though it's
> early days yet. It's not so good for Debian in terms of timing. We're
> not going to freeze for another 10 months, then the release will likely
> be at least 6 months after that. The earlier a kernel release we pick
> with, the more hardware support needs to be backported later. So,
> extrapolating the likely kernel release dates, I think I would prefer to
> use something between 3.2 and 3.4.
>
I'd *guess* Ubuntu 12.04 LTS goes for Linux 3.2 ..
-- Pasi
> As for the RT patchset, I haven't seen any announcement that it will
> continue to be developed against 3.0 after the release of 3.1. Of
> course, the fact that there *is* a working RT patchset for 3.0 is an
> advancement over recent upstream releases.
>
> Ben.
>
prev parent reply other threads:[~2011-08-18 12:11 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-15 4:15 Greg KH
2011-08-15 6:48 ` Jörg-Volker Peetz
2011-08-15 7:06 ` david
2011-08-15 7:16 ` Teck Choon Giam
2011-08-15 7:25 ` david
2011-08-15 7:38 ` Teck Choon Giam
2011-08-15 7:57 ` Jörg-Volker Peetz
2011-08-17 11:07 ` James Courtier-Dutton
2011-08-15 7:19 ` Jörg-Volker Peetz
2011-08-15 7:21 ` david
2011-08-15 14:21 ` Greg KH
2011-08-16 2:26 ` [Stable-review] " Ben Hutchings
2011-08-16 2:56 ` [stable] " Greg KH
2011-08-16 3:31 ` Ben Hutchings
2011-08-16 5:26 ` Daniel Taylor
2011-08-24 23:57 ` Greg KH
2011-08-15 7:33 ` [Stable-review] " Willy Tarreau
2011-08-15 14:18 ` [stable] " Greg KH
2011-08-15 15:04 ` [stable] " Tim Gardner
2011-08-16 2:09 ` [Stable-review] " Ben Hutchings
2011-08-16 2:57 ` [stable] " Greg KH
2011-08-16 19:26 ` Jeremiah C. Foster
2011-08-16 22:33 ` [stable] " Greg KH
2011-08-17 10:33 ` Jeremiah Foster
2011-08-17 20:20 ` david
2011-08-24 4:47 ` Greg KH
2011-08-24 4:46 ` Greg KH
2011-08-24 13:03 ` Jeremiah Foster
2011-08-16 23:01 ` Tim Bird
2011-08-17 4:58 ` Greg KH
2011-08-17 13:21 ` Mark Brown
2011-08-17 17:33 ` Brian Swetland
2011-08-24 4:57 ` Greg KH
2011-08-25 4:49 ` Brian Swetland
2011-08-26 0:03 ` Greg KH
2011-08-18 0:33 ` [Stable-review] " Ben Hutchings
2011-08-18 11:28 ` Pasi Kärkkäinen [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=20110818112806.GF32373@reaktio.net \
--to=pasik@iki.fi \
--cc=akpm@linux-foundation.org \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=ben@decadent.org.uk \
--cc=greg@kroah.com \
--cc=linux-kernel@vger.kernel.org \
--cc=stable-review@kernel.org \
--cc=stable@kernel.org \
--cc=tbird20d@gmail.com \
--cc=tim.bird@am.sony.com \
--cc=torvalds@linux-foundation.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