From: Andrew Cooper <andrew.cooper3@citrix.com>
To: Jan Beulich <jbeulich@suse.com>,
Oleksii Kurochko <oleksii.kurochko@gmail.com>
Cc: Andrew Cooper <andrew.cooper3@citrix.com>,
Community Manager <community.manager@xenproject.org>,
"committers@xenproject.org" <committers@xenproject.org>,
Xen-devel <xen-devel@lists.xenproject.org>
Subject: Re: Code freeze for 4.22 started on May 11, 2026
Date: Mon, 11 May 2026 14:57:52 +0100 [thread overview]
Message-ID: <d3f3e745-6d24-4e41-b8bb-de7145a3b2ea@citrix.com> (raw)
In-Reply-To: <4b0f55a1-1e9b-4ce1-b6b6-29b868d57e25@suse.com>
On 11/05/2026 2: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.
This is updating/resyncing the mwait_idle driver with Linux. It is
necessary for new CPUs.
~Andrew
next prev parent reply other threads:[~2026-05-11 13:58 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-11 9:35 Code freeze for 4.22 started on May 11, 2026 Oleksii Kurochko
2026-05-11 9:41 ` Jan Beulich
2026-05-11 13:34 ` Oleksii Kurochko
2026-05-11 13:45 ` Jan Beulich
2026-05-11 13:57 ` Andrew Cooper [this message]
2026-05-11 14:24 ` Oleksii Kurochko
2026-05-11 18:53 ` Roger Pau Monné
2026-05-12 13:34 ` Oleksii Kurochko
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=d3f3e745-6d24-4e41-b8bb-de7145a3b2ea@citrix.com \
--to=andrew.cooper3@citrix.com \
--cc=committers@xenproject.org \
--cc=community.manager@xenproject.org \
--cc=jbeulich@suse.com \
--cc=oleksii.kurochko@gmail.com \
--cc=xen-devel@lists.xenproject.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.