From: "Daniel P. Berrangé" <berrange@redhat.com>
To: "Philippe Mathieu-Daudé" <philmd@linaro.org>
Cc: "Emilio Cota" <cota@braap.org>,
"Alex Bennée" <alex.bennee@linaro.org>,
"Richard Henderson" <richard.henderson@linaro.org>,
"Paolo Bonzini" <pbonzini@redhat.com>,
qemu-devel@nongnu.org
Subject: Re: [PATCH v2 0/2] fix for #285
Date: Mon, 20 Mar 2023 15:35:33 +0000 [thread overview]
Message-ID: <ZBh9RV8pKOU7A+jc@redhat.com> (raw)
In-Reply-To: <002645e6-75a0-0409-a0ae-90265e4e4d1c@linaro.org>
On Mon, Mar 20, 2023 at 04:05:01PM +0100, Philippe Mathieu-Daudé wrote:
> Hi Emilio,
>
> On 19/3/23 15:15, Emilio Cota wrote:
> > Ping. Any feedback on these two patches?
> >
> > https://patchew.org/QEMU/20230205163758.416992-1-cota@braap.org/
> > https://lore.kernel.org/qemu-devel/20230205163758.416992-1-cota@braap.org/
> >
> > Happy to resend if needed.
>
> Since we are past hard-freeze, this series likely missed the v8.0
> release IMO. Note that doesn't mean maintainers can't queue it and
> send the pull request later when the next development window opens.
This series is a bug fix though, the freeze only applies to
features. For rc0/1 most bug fixes are still permissible.
I'd really recommend we take this series, as it is a clear
bug in linux-user that can be fairly easily reproduced
With regards,
Daniel
--
|: https://berrange.com -o- https://www.flickr.com/photos/dberrange :|
|: https://libvirt.org -o- https://fstop138.berrange.com :|
|: https://entangle-photo.org -o- https://www.instagram.com/dberrange :|
next prev parent reply other threads:[~2023-03-20 15:36 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-05 16:37 [PATCH v2 0/2] fix for #285 Emilio Cota
2023-02-05 16:37 ` [PATCH v2 1/2] util: import GTree as QTree Emilio Cota
2023-02-05 16:37 ` [PATCH v2 2/2] tcg: use QTree instead of GTree Emilio Cota
2023-03-21 16:23 ` Philippe Mathieu-Daudé
2023-02-17 12:44 ` [PATCH v2 0/2] fix for #285 Emilio Cota
2023-03-19 14:15 ` Emilio Cota
2023-03-20 15:05 ` Philippe Mathieu-Daudé
2023-03-20 15:35 ` Daniel P. Berrangé [this message]
2023-03-21 17:55 ` Richard Henderson
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=ZBh9RV8pKOU7A+jc@redhat.com \
--to=berrange@redhat.com \
--cc=alex.bennee@linaro.org \
--cc=cota@braap.org \
--cc=pbonzini@redhat.com \
--cc=philmd@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=richard.henderson@linaro.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).