Re: [PATCH 5.19 000/717] 5.19.17-rc1 review

From: Greg Kroah-Hartman
Date: Sat Oct 22 2022 - 07:39:31 EST


On Sat, Oct 22, 2022 at 01:15:26PM +0200, Pavel Machek wrote:
> Hi!
>
> > > > This is the start of the stable review cycle for the 5.19.17 release.
> > > > There are 717 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 me know.
> > > >
> > > > Note, this will be the LAST 5.19.y kernel to be released. Please move
> > > > to the 6.0.y kernel branch at this point in time, as after this is
> > > > released, this branch will be end-of-life.
> > > >
> > >
> > > Hi Greg, thanks for the patch series, which is out three days after
> > > the -rc1 have been pused. As usual, the template message follows.
> >
> > What exactly do you mean by "3 days after"?
> >
> > Are you watching the linux-stable-rc branches? Those are there only for
> > CI systems and are not a "real" -rc release at all until we do this
> > email announcement.
> >
> > The -rc1 release here does not look at all like what was in the
> > linux-stable-rc branch 3 days ago if you look closely. There are a lot
> > fewer patches now than before, and other changes.
> >
> > So again, unless you are running a CI system, don't look at the
> > linux-stable-rc branches.
>
> What do you suggest for people trying to review -stable? Two days are
> not enough to review 500 patches...

There's 717 patches here, more than 500 :)

Almost all of these have been in the stable queue for a full week now,
if not longer. Almost all of these were already in the last 6.0.y
review cycle and release also, so you all should have already seen these
before, and maintainers have had a chance to weigh in on them.

Kernel development is constantly going faster this year than last year,
that's something that has always been the case, so having more patches
in stable is also a constant.

Also, there's no requirement that you have to review them all, right?
Review the ones that you care about in your subsystems and all is good.

thanks,

greg k-h