From: Zhao Liu <zhao1.liu@intel.com>
To: "Philippe Mathieu-Daudé" <philmd@linaro.org>
Cc: Juan Quintela <juan.quintela@gmail.com>,
Eduardo Habkost <eduardo@habkost.net>,
"Michael S. Tsirkin" <mst@redhat.com>,
afaerber@suse.de, ale@rev.ng, anjo@rev.ng, bbauman@redhat.com,
chao.p.peng@linux.intel.com, cjia@nvidia.com, cw@f00f.org,
eblake@redhat.com, edgar.iglesias@gmail.com,
elena.ufimtseva@oracle.com, eric.auger@redhat.com,
f4bug@amsat.org,
"felipe@nutanix.com" <felipe.franciosi@nutanix.com>,
"iggy@theiggy.com" <iggy@kws1.com>,
"imp@bsdimp.com" <wlosh@bsdimp.com>,
jan.kiszka@web.de, jgg@nvidia.com, jidong.xiao@gmail.com,
jjherne@linux.vnet.ibm.com, joao.m.martins@oracle.com,
konrad.wilk@oracle.com, mburton@qti.qualcomm.com,
mdean@redhat.com, mimu@linux.vnet.ibm.com,
peter.maydell@linaro.org, qemu-devel@nongnu.org,
quintela@redhat.com, richard.henderson@linaro.org,
shameerali.kolothum.thodi@huawei.com, stefanha@gmail.com,
wei.w.wang@intel.com, z.huo@139.com, zwu.kernel@gmail.com,
Zhenyu Wang <zhenyu.z.wang@intel.com>,
Zhao Liu <zhao1.liu@intel.com>
Subject: Re: QEMU developers fortnightly conference call for agenda for 2023-12-12
Date: Tue, 12 Dec 2023 10:13:25 +0800 [thread overview]
Message-ID: <ZXfBxcGGqE0t2SpC@intel.com> (raw)
In-Reply-To: <e2462fb5-228a-443d-93ce-7069998128b0@linaro.org>
Hi Philippe,
On Mon, Dec 11, 2023 at 08:04:28PM +0100, Philippe Mathieu-Daudé wrote:
> Date: Mon, 11 Dec 2023 20:04:28 +0100
> From: Philippe Mathieu-Daudé <philmd@linaro.org>
> Subject: Re: QEMU developers fortnightly conference call for agenda for
> 2023-12-12
>
> Hi Zhao,
>
[snip]
>
> FYI I have your series tagged for review (for generic QOM /
> machine [*]) but we need feedback from the x86 maintainers too,
> and eventually from riscv/arm too, since they might end up
> using your API.
>
> [*] That said, I unlikely will have time the next 2 weeks.
Thanks for your help!
Best Regards,
Zhao
>
> Regards,
>
> Phil.
>
> > Thanks,
> > Zhao
>
next prev parent reply other threads:[~2023-12-12 2:02 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-05 13:47 QEMU developers fortnightly conference call for agenda for 2023-12-12 Juan Quintela
2023-12-05 14:58 ` Het Gala
2023-12-11 13:29 ` Zhao Liu
2023-12-11 16:37 ` Zhao Liu
2023-12-11 19:04 ` Philippe Mathieu-Daudé
2023-12-12 2:13 ` Zhao Liu [this message]
2023-12-11 18:49 ` 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=ZXfBxcGGqE0t2SpC@intel.com \
--to=zhao1.liu@intel.com \
--cc=afaerber@suse.de \
--cc=ale@rev.ng \
--cc=anjo@rev.ng \
--cc=bbauman@redhat.com \
--cc=chao.p.peng@linux.intel.com \
--cc=cjia@nvidia.com \
--cc=cw@f00f.org \
--cc=eblake@redhat.com \
--cc=edgar.iglesias@gmail.com \
--cc=eduardo@habkost.net \
--cc=elena.ufimtseva@oracle.com \
--cc=eric.auger@redhat.com \
--cc=f4bug@amsat.org \
--cc=felipe.franciosi@nutanix.com \
--cc=iggy@kws1.com \
--cc=jan.kiszka@web.de \
--cc=jgg@nvidia.com \
--cc=jidong.xiao@gmail.com \
--cc=jjherne@linux.vnet.ibm.com \
--cc=joao.m.martins@oracle.com \
--cc=juan.quintela@gmail.com \
--cc=konrad.wilk@oracle.com \
--cc=mburton@qti.qualcomm.com \
--cc=mdean@redhat.com \
--cc=mimu@linux.vnet.ibm.com \
--cc=mst@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=philmd@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=quintela@redhat.com \
--cc=richard.henderson@linaro.org \
--cc=shameerali.kolothum.thodi@huawei.com \
--cc=stefanha@gmail.com \
--cc=wei.w.wang@intel.com \
--cc=wlosh@bsdimp.com \
--cc=z.huo@139.com \
--cc=zhenyu.z.wang@intel.com \
--cc=zwu.kernel@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.