From: "Philippe Mathieu-Daudé" <philmd@linaro.org>
To: Juan Quintela <juan.quintela@gmail.com>,
afaerber@suse.de, ale@rev.ng, anjo@rev.ng, bazulay@redhat.com,
bbauman@redhat.com, chao.p.peng@linux.intel.com, cjia@nvidia.com,
cw@f00f.org, david.edmondson@oracle.com,
dustin.kirkland@canonical.com, 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
Subject: Re: QEMU developers fortnightly conference call for 2023-10-31
Date: Mon, 30 Oct 2023 15:56:44 +0100 [thread overview]
Message-ID: <597d5991-97c5-9e2e-0660-fe5c75b3b1b7@linaro.org> (raw)
In-Reply-To: <calendar-1ad16449-09cc-40fb-ab4a-24eafcc62d2a@google.com>
Hi Juan,
On 30/10/23 12:04, Juan Quintela wrote:
> QEMU developers fortnightly conference call
>
> Hi
>
> If you have any topics for this week Conference call, please answer to
> this email.
I don't have anything planned but I can take 30min to briefly
describe the problems I'm encountering, and present the vision /
roadmap prepared, which I'll post as RFC soon (right know I'm
focusing on getting my last PRs ready for soft freeze).
> Thanks, Juan.
>
> QEMU developers fortnightly conference call
> Tuesday 2023-10-31 ⋅ 14:00 – 15:00 (Central European Time - Madrid)
> If you need call details, please contact me: quintela@redhat.com
> <mailto:quintela@redhat.com>
>
>
> Location
>
> https://meet.jit.si/kvmcallmeeting
> View map
> <https://www.google.com/url?q=https%3A%2F%2Fmeet.jit.si%2Fkvmcallmeeting&sa=D&ust=1699095840000000&usg=AOvVaw2MfLnjN20yFq03yus22z_j>
next prev parent reply other threads:[~2023-10-30 14:57 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-30 11:04 QEMU developers fortnightly conference call for 2023-10-31 Juan Quintela
2023-10-30 14:56 ` Philippe Mathieu-Daudé [this message]
2023-10-31 12:53 ` Philippe Mathieu-Daudé
2023-10-31 18:26 ` 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=597d5991-97c5-9e2e-0660-fe5c75b3b1b7@linaro.org \
--to=philmd@linaro.org \
--cc=afaerber@suse.de \
--cc=ale@rev.ng \
--cc=anjo@rev.ng \
--cc=bazulay@redhat.com \
--cc=bbauman@redhat.com \
--cc=chao.p.peng@linux.intel.com \
--cc=cjia@nvidia.com \
--cc=cw@f00f.org \
--cc=david.edmondson@oracle.com \
--cc=dustin.kirkland@canonical.com \
--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=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 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).