On Wed, Oct 28, 2026 at 2:01 AM Borislav Petkov <[email protected]> wrote: > > On Tue, Oct 20, 2026 at 11:34:23PM -0400, Zack Rusin wrote: > > Gentle ping on this one. It's a stable fix for the i386 high-bandwidth > > hypercalls (vmwgfx uses them), Maaz reviewed it, and it still applies > > cleanly to v7.3. The hypercall cleanup series I'm about to post moves > > this assembly out of line and is based on it, so it would help to know > > whether it's queued or needs changes. > > Sashiko complains about some pre-existing issues: > > https://sashiko.dev/#/patchset/4ab10678a8f50053934b62b56af81f881c1d3798.1788414669.git.zack.rusin%40broadcom.com > > Please address them: if valid, you should see about fixing them, if not, > explain why they don't need to be fixed.
I haven't seen this. I need to update my kernel setup to fetch those muted Sashiko reports. Anyway, both are valid but they're preexisting issues in vmwgfx. I was planning to rip out most of that code in vmwgfx but I can provide fixes for these two. We could land them via your tree if you need them as a prerequisite for landing the above, I'll just make sure nothing touches that code via the drm tree while the changes are staged in yours. Or I can send out the vmwgfx fixes to dri-devel and land them in parallel via the regular drm tree. Let me know what you prefer. z
smime.p7s
Description: S/MIME Cryptographic Signature
