From: Zhao Liu <zhao1.liu@intel.com>
To: Juan Quintela <juan.quintela@gmail.com>
Cc: 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: Mon, 11 Dec 2023 21:29:24 +0800 [thread overview]
Message-ID: <ZXcOtAIMqLjOheIa@intel.com> (raw)
In-Reply-To: <calendar-98548e19-3517-40fa-a2ae-1c384aa3f98f@google.com>
Hi Juan,
On Tue, Dec 05, 2023 at 01:47:52PM +0000, Juan Quintela wrote:
> Date: Tue, 05 Dec 2023 13:47:52 +0000
> From: Juan Quintela <juan.quintela@gmail.com>
> Subject: QEMU developers fortnightly conference call for agenda for
> 2023-12-12
>
> Hi If you have any topics for the last qemu conference call of the year,
> feel free to answer to this email. Later, Juan.
>
> QEMU developers fortnightly conference call
> Tuesday 2023-12-12 ⋅ 15:00 – 16:00
> Central European Time - Madrid
>
> Location
> https://meet.jit.si/kvmcallmeeting
> https://www.google.com/url?q=https%3A%2F%2Fmeet.jit.si%2Fkvmcallmeeting&sa=D&ust=1702216020000000&usg=AOvVaw1xrpPSmMRu9niy1trqCKrA
>
I want to talk about the RFC about QOM topology:
https://lore.kernel.org/qemu-devel/20231130144203.2307629-1-zhao1.liu@linux.intel.com/
We would like to receive the initial feedback from the community on this
direction to see if we are on the right track.
Thanks,
Zhao
>
>
> If you need call details, please contact me: quintela@redhat.com
>
> Guests
> Philippe Mathieu-Daudé
> Joao Martins
> quintela@redhat.com
> mdean@redhat.com
> felipe@nutanix.com
> afaerber@suse.de
> bbauman@redhat.com
> cw@f00f.org
> eblake@redhat.com
> edgar.iglesias@gmail.com
> eric.auger@redhat.com
> iggy@theiggy.com
> jan.kiszka@web.de
> jidong.xiao@gmail.com
> jjherne@linux.vnet.ibm.com
> mimu@linux.vnet.ibm.com
> peter.maydell@linaro.org
> richard.henderson@linaro.org
> stefanha@gmail.com
> imp@bsdimp.com
> z.huo@139.com
> zwu.kernel@gmail.com
> jgg@nvidia.com
> cjia@nvidia.com
> Elena Ufimtseva
> konrad.wilk@oracle.com
> ale@rev.ng
> anjo@rev.ng
> Shameerali Kolothum Thodi
> wei.w.wang@intel.com
> Chao Peng
> qemu-devel@nongnu.org
> mburton@qti.qualcomm.com
>
>
next prev parent reply other threads:[~2023-12-11 13:17 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 [this message]
2023-12-11 16:37 ` Zhao Liu
2023-12-11 19:04 ` Philippe Mathieu-Daudé
2023-12-12 2:13 ` Zhao Liu
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=ZXcOtAIMqLjOheIa@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=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=peter.maydell@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.