public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Paul Gortmaker <paul.gortmaker@windriver.com>
To: Greg KH <greg@kroah.com>,
	linux-kernel@vger.kernel.org,
	Andrew Morton <akpm@linux-foundation.org>,
	torvalds@linux-foundation.org, stable@kernel.org,
	jason.wessel@windriver.com
Cc: Andi Kleen <andi@firstfloor.org>, lwn@lwn.net
Subject: Announcement: Plans for v2.6.34-longterm
Date: Fri, 3 Dec 2010 16:07:19 -0500	[thread overview]
Message-ID: <20101203210719.GB21223@windriver.com> (raw)

Firstly, I'd like to thank Greg for all the past work he's done on
juggling all these different stable releases - many people have
reaped the benefits of them for quite some time, and it only makes
sense to spread the loading around as it has grown significantly.

With that in mind, it is our intention to also maintain a 2.6.34
longterm tree.  Jason and I work at Wind River, which already has
released products based on v2.6.34, and as such it only makes sense
to have a public long-term tree that others who are also based on
2.6.34 can make use of.

I've already done an end-to-end audit of the current 2.6.32 longterm
stable release, and used the list of these already "approved for stable"
patches on v2.6.32 to identify 260 upstream commits that are applicable,
but not yet present in the last 2.6.34.7 stable release.

A candidate tree for 2.6.34.8 with the above 260 commits applied to
it is available now for review/testing at:

   git://git.kernel.org/pub/scm/linux/kernel/git/paulg/linux-2.6.34.y.git

Note that there are no additional "non-stable" commits applied to this
tree.  It is purely commits that are already in use in a stable release.
The next step will be to audit the 35-stable for appropriate content.

This tree is currently undergoing internal testing at WR on various
x86[64], ARM, MIPS and PowerPC targets, but of course any additional
testing and feedback is most welcome.  If anyone is interested in the
audit data, I can send folks details on that too.

Just as with Andi's longterm tree, the final details of where these
will be finally located on kernel.org and so forth remains to be worked
out and will be announced at a later date as things are finalized.

Paul.

             reply	other threads:[~2010-12-03 21:09 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-12-03 21:07 Paul Gortmaker [this message]
2010-12-04 17:27 ` Announcement: Plans for v2.6.34-longterm Greg KH
2010-12-05  0:45   ` Paul Gortmaker
2010-12-04 17:28 ` Greg KH
2010-12-05  1:16   ` Paul Gortmaker
2010-12-05 16:50     ` Greg KH
2010-12-06  4:54       ` Bruce Ashfield
2010-12-06  5:35   ` Minchan Kim
2010-12-06  6:01     ` Minchan Kim
2011-11-08 22:14 ` George G. Davis
2011-11-08 23:11   ` Paul Gortmaker
2011-11-08 23:52     ` Greg KH
2011-11-09  3:20       ` Paul Gortmaker
2011-11-10 19:54         ` Greg KH
2011-11-10 20:29           ` Paul Gortmaker
2011-11-09 17:12     ` George G. Davis

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=20101203210719.GB21223@windriver.com \
    --to=paul.gortmaker@windriver.com \
    --cc=akpm@linux-foundation.org \
    --cc=andi@firstfloor.org \
    --cc=greg@kroah.com \
    --cc=jason.wessel@windriver.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lwn@lwn.net \
    --cc=stable@kernel.org \
    --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