Re: [PATCH 00/32] x86/msr: Drop 32-bit MSR interfaces

From
Juergen Gross <jgross@suse.com>
Date
2026-07-02 11:03:58
Also in
dri-devel, kvm, linux-acpi, linux-coco, linux-crypto, linux-edac, linux-gpio, linux-hwmon, linux-hyperv, linux-ide, linux-pci, linux-perf-users, linux-pm, lkml, platform-driver-x86, virtualization, xen-devel
Reply to
Ingo Molnar, 2026-07-02
On 02.07.26 12:07, Ingo Molnar wrote:
* Sean Christopherson [off-list ref] wrote:
quoted
quoted
Note that the individual patches are IMO significantly easier to review
through the actual 32-bit => 64-bit variable assignment changes done
in isolation (which sometimes include minor cleanups), while
the Coccinelle semantic patch:

    { a(b,c) => c = a(b) }

which changes both the function signature and the order of terms as
well, is just a single add-on treewide patch.
Is the plan for subsystem maintainers to pick up the relevant patches,
and then do the treewide change one release cycle later?
I'll try to keep the patches in a single tree (tip:x86/msr)
in the hope of not prolonging the pain two cycles - but it's
of course fine for maintainers to pick up the patches too
(most of them are standalone), we'll sort it all out in the end.
Ingo, would you be fine with me posting patch updates just as replies to the
original patch emails? This would speed things up, as I wouldn't need to wait
for more review input of all the patches before sending out new versions.

As the patches are (mostly) standalone, this should not cause any weird
problems.

The last two patches might need updates, but those can be applied only after
the rest has been accepted anyway.


Juergen

Attachments

Thread (15 messages) 15 messages, 5 authors, last reply 2026-07-17
Keyboard shortcuts
hback out one level
jnext message in thread / next series-diff position
kprevious message in thread / previous series-diff position
ldrill in
Escclose help / fold thread tree
?toggle this help