From: Peter Xu <peterx@redhat.com>
To: "Philippe Mathieu-Daudé" <philmd@linaro.org>
Cc: qemu-devel@nongnu.org, Juan Quintela <quintela@redhat.com>,
Gerd Hoffmann <kraxel@redhat.com>,
Fabiano Rosas <farosas@suse.de>
Subject: Re: [PATCH] hw/audio/sb16: Do not migrate qdev properties
Date: Fri, 5 Jan 2024 09:59:56 +0800 [thread overview]
Message-ID: <ZZdinF59FrEJDhhZ@x1n> (raw)
In-Reply-To: <48dcbec1-dceb-4bfe-8876-96b99c8ed6c7@linaro.org>
On Thu, Jan 04, 2024 at 05:48:18PM +0100, Philippe Mathieu-Daudé wrote:
> If there are no objections I'll queue this patch (fixing
> the typo reported by Zoltan).
Yes feel free to. Thanks,
--
Peter Xu
next prev parent reply other threads:[~2024-01-05 2:01 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-24 18:26 [PATCH] hw/audio/sb16: Do not migrate qdev properties Philippe Mathieu-Daudé
2023-12-13 17:36 ` Philippe Mathieu-Daudé
2023-12-13 19:34 ` BALATON Zoltan
2024-01-04 16:48 ` Philippe Mathieu-Daudé
2024-01-04 17:05 ` Fabiano Rosas
2024-01-05 1:59 ` Peter Xu [this message]
2024-01-05 22:01 ` Philippe Mathieu-Daudé
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=ZZdinF59FrEJDhhZ@x1n \
--to=peterx@redhat.com \
--cc=farosas@suse.de \
--cc=kraxel@redhat.com \
--cc=philmd@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=quintela@redhat.com \
/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).