Re: [patch 00/33] 2.6.20-stable review

From: Jesper Juhl
Date: Fri Apr 27 2007 - 07:06:14 EST

On 27/04/07, Wu, Bryan <bryan.wu@xxxxxxxxxx> wrote:
On Thu, 2007-04-26 at 09:54 -0700, Greg KH wrote:
> This is the start of the stable review cycle for the release.
> There are 33 patches in this series, all will be posted as a response to
> this one. If anyone has any issues with these being applied, please let
> us know. If anyone is a maintainer of the proper subsystem, and wants
> to add a Signed-off-by: line to the patch, please respond with it.
> These patches are sent out with a number of different people on the Cc:
> line. If you wish to be a reviewer, please email stable@xxxxxxxxxx to
> add your name to the list. If you want to be off the reviewer list,
> also email us.

Hi Greg:

I am just wondering that is there any rule for stable kernel version

AFAIK, 2.6.x kernels are all stable release and 2.6.x.y is for stable
tree bug fixing and long term supporting. But I found 2.6.16.y got 49
version updating, it is more active than other stable release such as
2.6.17 and 2.6.19. It looks like 2.6.16 is a long-long term supporting
version and even number 2.6.x kernel is more active than odd number
2.6.x kernel.

You know for some customer's product, they want to use the stable and
long term support kernel instead to use the latest one.

Could you please give us some idea about this regular?

2.6.16.y is special in that Adrian Bunk took it upon himself to
maintain that branch more or less indefinately. But that's not how
-stable normally works, it's Adrians own project.

The normal way -stable works is that it tracks the latest 2.6.x kernel
that has been released.
Now that 2.6.21 has been released, a final flush of the patch queue
against 2.6.20 is done, that will be, and then -stable will
switch to 2.6.21.y, when 2.6.22 comes out a final 2.6.21.y is made and
then it's off to track 2.6.22

The rules for what is suitable for a -stable release etc is written in

I believe the above reflects reality - if I've said something wrong I
assume Greg will correct me :)

Jesper Juhl <jesper.juhl@xxxxxxxxx>
Don't top-post
Plain text mails only, please
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at
Please read the FAQ at