For those of you who haven't waded through the huge "RFD: Kernel releasenumbering" thread on lkml to realize that we are now going to startputting out 2.6.x.y releases, here's the summary:

A few of us $suckers will be trying to maintain a 2.6.x.y set of releases that happen after 2.6.x is released. It will contain only a set of bugfixes and security fixes that meet a strict set of guidelines, as defined by Linus at:http://article.gmane.org/gmane.linux.kernel/283396

Chris Wright and I are going to start working on doing this work, wewill have a <SOME_ALIAS>@kernel.org to post these types of bug fixes to,and a set of people we bounce the patches off of to test for "smellsgood" validation. We will also have a bk-commits type mailing list forthose who want to watch the patches flow in, and a bk tree from whichchangsets can be pulled from.

Chris and I will be hashing all of the details out next Tuesday, andhopefully all the infrastructure will be in place soon. When thathappens, we will post the full details on how all of this is going towork. In the meantime, feel free to CC: me and Chris on patches thateveryone thinks should go into the 2.6.11.y releases.

But right now, Chris is on a plane, and we don't have the email aliasset up, or the proper permissions set up on kernel.org to push changesinto the v2.6 directory, but we have a few bugs that are needing to befixed in the 2.6.11 release. And since our mantra is, "release earlyand often", here's the first release.

---------------I've released the 2.6.11.1 patch: kernel.org/pub/linux/kernel/people/gregkh/v2.6.11/patch-2.6.11.1.gz

With a detailed changelog at: kernel.org/pub/linux/kernel/people/gregkh/v2.6.11/ChangeLog-2.6.11.1

A bitkeeper tree for the 2.6.11.y releases can be found at: bk://linux-release.bkbits.net/linux-2.6.11

The diffstat and short summary of the fixes are below.

I'll also be replying to this message with a copy of the patch itself,as it is small enough to do so.