Re: Code freeze for 4.22 started on May 11, 2026

[Oleksii Kurochko <oleksii.kurochko@xxxxxxxxx>]

On 5/11/26 3:45 PM, Jan Beulich wrote:
> On 11.05.2026 15:34, Oleksii Kurochko wrote:
> > On 5/11/26 11:41 AM, Jan Beulich wrote:
> > > On 11.05.2026 11:35, Oleksii Kurochko wrote:
> > > > I would like to inform you that Code freeze period is started and will
> > > > be until Fri Jun 05, 2026 (+4 weeks from Feature freeze).
> > > >
> > > > Bugfixes may continue to be accepted by maintainers without R-Ack.
> > > Gives me context to ask right away: "x86/mwait-idle: sync up with Linux
> > > 7.0-rc" has had a few small adjustments and hence would want re-posting.
> > > Question is: Does that even make sense at this point, i.e. would you
> > > give it a release-ack despite it not all being bug fixes?
> > I don't see any Fixes: tag in the mentioned patch series and also based
> > on cover letter it doesn't really clear what this patch series is fixing.
> >
> > Could you please clarify?
> It is "fixing" us lagging behind the Linux driver that ours was cloned
> from. Plus the series was posted well in time.
It was posted well in time but it wasn't committed before Code freeze 
started.
But considering that it is necessary for new CPUs (as Andrew C. 
mentioned in one of reply) we want to have that in release.
~ Oleksii