On 15/02/2026 23:20, Thomas Huth wrote:
On 16/02/2026 02.12, Yodel Eldar wrote:
...
Thomas and Akihiko, if it's alright with you, could we delay the PR of
the revert at least until we sort this out? I realize the erratic
timeouts are gumming up the CI, but maybe we could reduce the deltas of
the git history in short order if it's not too much trouble? I can
submit the patch in one to two days; I just want to make sure it's done
correctly.
Hi!
Sorry, but it has already been reverted:
https://gitlab.com/qemu-project/qemu/-/commit/
ddb4d9d1748681cfde824d765af6
... but that should not be a big deal, simply submit the patch again
once you've got a proper fix for the problem.
Regards,
Thomas
Ah, it was already part of that set! Thanks for letting me know. I
suppose that softens the sense of urgency with the fix; nonetheless,
I'll aim for sooner rather than later.
I'm inclined to squash the fix into the re-introduction (especially when
the fix is small in scope), or should they be separate commits since the
original patch and the fix touch different subsystems? For the latter, I
think the fix can precede the re-introductory commit (as suggested by a
quick cherry-pick and replay test run), so as to avoid poisoning
bisectability.
Yodel
