public inbox for linux-rt-users@vger.kernel.org
 help / color / mirror / Atom feed
From: Thomas Gleixner <tglx@linutronix.de>
To: Ng Oon-Ee <ngoonee@gmail.com>
Cc: Andres Cimmarusti <acimmarusti@gmail.com>,
	linux-rt-users@vger.kernel.org
Subject: Re: RT support for LTS kernel 2.6.32 ?
Date: Fri, 23 Jul 2010 12:37:13 +0200 (CEST)	[thread overview]
Message-ID: <alpine.LFD.2.00.1007231232310.2616@localhost.localdomain> (raw)
In-Reply-To: <1279838130.19144.4.camel@localhost.localdomain>

On Fri, 23 Jul 2010, Ng Oon-Ee wrote:

> On Thu, 2010-07-22 at 15:51 -0400, Andres Cimmarusti wrote:
> > Hi,
> > 
> > I saw in the kernel archives that the only recent kernels supported by
> > the patch are 2.6.33.x. I was wondering if there will be any support
> > for the 2.6.32.x kernels which will be long term supported and
> > prominent distros like Ubuntu LTS 10.04 and Debian Squeeze 6.0 are
> > based on them.
> > 
> > Thanks
> > 
> > Andres
> 
> I think the decision was taken to only support odd-numbered kernels. For
> example the current 2.6.34 will not have a release either.

The decision to provide RT for a given mainline version is based on
bandwidth constraints of the developers, testing capacities and the
required stabilization period. There are other factors as well,
e.g. we skipped 32 simply because we were able to merge quite a chunk
of RT code into 33, which made life easier. So there is no rule which
mainline version we pick, but I can confirm that 34 will not have a RT
release.

Thanks,

	tglx

      reply	other threads:[~2010-07-23 10:37 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-07-22 19:51 RT support for LTS kernel 2.6.32 ? Andres Cimmarusti
2010-07-22 22:35 ` Ng Oon-Ee
2010-07-23 10:37   ` Thomas Gleixner [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=alpine.LFD.2.00.1007231232310.2616@localhost.localdomain \
    --to=tglx@linutronix.de \
    --cc=acimmarusti@gmail.com \
    --cc=linux-rt-users@vger.kernel.org \
    --cc=ngoonee@gmail.com \
    /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