From: Richard Henderson <richard.henderson@linaro.org>
To: "Michael Tokarev" <mjt@tls.msk.ru>,
"Daniel P. Berrangé" <berrange@redhat.com>
Cc: "QEMU Developers" <qemu-devel@nongnu.org>,
"Alex Bennée" <alex.bennee@linaro.org>,
"Paul Menzel" <pmenzel@molgen.mpg.de>,
"Philippe Mathieu-Daudé" <philmd@linaro.org>
Subject: Re: stable-8.1.1: which bug do we keep?
Date: Thu, 28 Sep 2023 10:24:02 -0700 [thread overview]
Message-ID: <bcc10b9c-d53a-63c7-9a9e-64b3960ae8e3@linaro.org> (raw)
In-Reply-To: <688aae83-b8fb-5867-2451-dc0c67fe9319@tls.msk.ru>
On 9/20/23 16:45, Michael Tokarev wrote:
> 20.09.2023 12:17, Daniel P. Berrangé wrote:
>> Since the 2nd series is shown to still be broken in some cases
>> and 1st is thought to solve them all, IMHO it feels like we
>> should just press ahead with applying the the 1st series to
>> git master, and then stable.
>>
>> If we still want a cleaner solution, it can be reverted/replaced
>> later once someone figures out an option that addresses all the
>> problems. We shouldn't leave such a big regression in TCG unfixed
>> for so long while we figure out a cleaner option.
>
> Daniel, you have a very good point here.
>
> I just collected the first version of Richard's fixes (with Phil's
> changes and tags), added them to qemu debian package and pushed that
> one out, - debian has much wider CI than qemu has, hopefully it will
> clear things out.
Thanks for that. Any surprises?
The timing of all this has been poor, coming just before I've been away for a few weeks.
I plan to get the can_do_io patch set upstreamed soon.
r~
next prev parent reply other threads:[~2023-09-28 17:24 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-20 4:46 stable-8.1.1: which bug do we keep? Michael Tokarev
2023-09-20 9:17 ` Daniel P. Berrangé
2023-09-20 20:45 ` Michael Tokarev
2023-09-28 17:24 ` Richard Henderson [this message]
2023-09-28 17:31 ` Michael Tokarev
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=bcc10b9c-d53a-63c7-9a9e-64b3960ae8e3@linaro.org \
--to=richard.henderson@linaro.org \
--cc=alex.bennee@linaro.org \
--cc=berrange@redhat.com \
--cc=mjt@tls.msk.ru \
--cc=philmd@linaro.org \
--cc=pmenzel@molgen.mpg.de \
--cc=qemu-devel@nongnu.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).