* Code freeze for 4.22 started on May 11, 2026
@ 2026-05-11 9:35 Oleksii Kurochko
2026-05-11 9:41 ` Jan Beulich
2026-05-11 18:53 ` Roger Pau Monné
0 siblings, 2 replies; 8+ messages in thread
From: Oleksii Kurochko @ 2026-05-11 9:35 UTC (permalink / raw)
To: Xen-devel; +Cc: Community Manager, committers@xenproject.org
Hello everyone,
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.
Thanks in advance. Have a good week.
~ Oleksii
^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: Code freeze for 4.22 started on May 11, 2026
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 18:53 ` Roger Pau Monné
1 sibling, 1 reply; 8+ messages in thread
From: Jan Beulich @ 2026-05-11 9:41 UTC (permalink / raw)
To: Oleksii Kurochko; +Cc: Community Manager, committers@xenproject.org, Xen-devel
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?
Jan
^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: Code freeze for 4.22 started on May 11, 2026
2026-05-11 9:41 ` Jan Beulich
@ 2026-05-11 13:34 ` Oleksii Kurochko
2026-05-11 13:45 ` Jan Beulich
0 siblings, 1 reply; 8+ messages in thread
From: Oleksii Kurochko @ 2026-05-11 13:34 UTC (permalink / raw)
To: Jan Beulich; +Cc: Community Manager, committers@xenproject.org, Xen-devel
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?
~ Oleksii
^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: Code freeze for 4.22 started on May 11, 2026
2026-05-11 13:34 ` Oleksii Kurochko
@ 2026-05-11 13:45 ` Jan Beulich
2026-05-11 13:57 ` Andrew Cooper
2026-05-11 14:24 ` Oleksii Kurochko
0 siblings, 2 replies; 8+ messages in thread
From: Jan Beulich @ 2026-05-11 13:45 UTC (permalink / raw)
To: Oleksii Kurochko; +Cc: Community Manager, committers@xenproject.org, Xen-devel
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.
Jan
^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: Code freeze for 4.22 started on May 11, 2026
2026-05-11 13:45 ` Jan Beulich
@ 2026-05-11 13:57 ` Andrew Cooper
2026-05-11 14:24 ` Oleksii Kurochko
1 sibling, 0 replies; 8+ messages in thread
From: Andrew Cooper @ 2026-05-11 13:57 UTC (permalink / raw)
To: Jan Beulich, Oleksii Kurochko
Cc: Andrew Cooper, Community Manager, committers@xenproject.org,
Xen-devel
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
^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: Code freeze for 4.22 started on May 11, 2026
2026-05-11 13:45 ` Jan Beulich
2026-05-11 13:57 ` Andrew Cooper
@ 2026-05-11 14:24 ` Oleksii Kurochko
1 sibling, 0 replies; 8+ messages in thread
From: Oleksii Kurochko @ 2026-05-11 14:24 UTC (permalink / raw)
To: Jan Beulich; +Cc: Community Manager, committers@xenproject.org, Xen-devel
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
^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: Code freeze for 4.22 started on May 11, 2026
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 18:53 ` Roger Pau Monné
2026-05-12 13:34 ` Oleksii Kurochko
1 sibling, 1 reply; 8+ messages in thread
From: Roger Pau Monné @ 2026-05-11 18:53 UTC (permalink / raw)
To: Oleksii Kurochko; +Cc: Xen-devel, Community Manager, committers@xenproject.org
On Mon, May 11, 2026 at 11:35:55AM +0200, Oleksii Kurochko wrote:
> Hello everyone,
>
> 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.
Hello,
I would like to inquire about whether changing an option default value
could still be accepted:
https://lore.kernel.org/xen-devel/20260511185145.23750-1-roger.pau@citrix.com/
This is not new code, just changing a default. I believe this makes
dom0 PVH more usable out of the box (see commit message).
Thanks, Roger.
^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: Code freeze for 4.22 started on May 11, 2026
2026-05-11 18:53 ` Roger Pau Monné
@ 2026-05-12 13:34 ` Oleksii Kurochko
0 siblings, 0 replies; 8+ messages in thread
From: Oleksii Kurochko @ 2026-05-12 13:34 UTC (permalink / raw)
To: Roger Pau Monné
Cc: Xen-devel, Community Manager, committers@xenproject.org
Hello Roger,
On 5/11/26 8:53 PM, Roger Pau Monné wrote:
> On Mon, May 11, 2026 at 11:35:55AM +0200, Oleksii Kurochko wrote:
>> Hello everyone,
>>
>> 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.
>
> Hello,
>
> I would like to inquire about whether changing an option default value
> could still be accepted:
>
> https://lore.kernel.org/xen-devel/20260511185145.23750-1-roger.pau@citrix.com/
>
> This is not new code, just changing a default. I believe this makes
> dom0 PVH more usable out of the box (see commit message).
I am okay to have this patch in release.
~ Oleksii
^ permalink raw reply [flat|nested] 8+ messages in thread
end of thread, other threads:[~2026-05-12 13:34 UTC | newest]
Thread overview: 8+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
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
2026-05-11 14:24 ` Oleksii Kurochko
2026-05-11 18:53 ` Roger Pau Monné
2026-05-12 13:34 ` Oleksii Kurochko
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.