From: Juan Quintela <juan.quintela@gmail.com>
To: Mark Burton <mburton@qti.qualcomm.com>
Cc: "afaerber@suse.de" <afaerber@suse.de>,
Alessandro Di Federico <ale@rev.ng>,
"anjo@rev.ng" <anjo@rev.ng>,
"bazulay@redhat.com" <bazulay@redhat.com>,
"bbauman@redhat.com" <bbauman@redhat.com>,
"chao.p.peng@linux.intel.com" <chao.p.peng@linux.intel.com>,
"cjia@nvidia.com" <cjia@nvidia.com>, "cw@f00f.org" <cw@f00f.org>,
"david.edmondson@oracle.com" <david.edmondson@oracle.com>,
"dustin.kirkland@canonical.com" <dustin.kirkland@canonical.com>,
"eblake@redhat.com" <eblake@redhat.com>,
"edgar.iglesias@gmail.com" <edgar.iglesias@gmail.com>,
"elena.ufimtseva@oracle.com" <elena.ufimtseva@oracle.com>,
"eric.auger@redhat.com" <eric.auger@redhat.com>,
"f4bug@amsat.org" <f4bug@amsat.org>,
Felipe Franciosi <felipe.franciosi@nutanix.com>,
"iggy@theiggy.com" <iggy@kws1.com>,
Warner Losh <wlosh@bsdimp.com>,
"jan.kiszka@web.de" <jan.kiszka@web.de>,
"jgg@nvidia.com" <jgg@nvidia.com>,
"jidong.xiao@gmail.com" <jidong.xiao@gmail.com>,
"jjherne@linux.vnet.ibm.com" <jjherne@linux.vnet.ibm.com>,
"joao.m.martins@oracle.com" <joao.m.martins@oracle.com>,
"konrad.wilk@oracle.com" <konrad.wilk@oracle.com>,
"mdean@redhat.com" <mdean@redhat.com>,
"mimu@linux.vnet.ibm.com" <mimu@linux.vnet.ibm.com>,
"peter.maydell@linaro.org" <peter.maydell@linaro.org>,
"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>,
"richard.henderson@linaro.org" <richard.henderson@linaro.org>,
"shameerali.kolothum.thodi@huawei.com"
<shameerali.kolothum.thodi@huawei.com>,
"stefanha@gmail.com" <stefanha@gmail.com>,
"wei.w.wang@intel.com" <wei.w.wang@intel.com>,
"z.huo@139.com" <z.huo@139.com>,
"zwu.kernel@gmail.com" <zwu.kernel@gmail.com>
Subject: Re: QEMU developers fortnightly conference for 2023-08-08
Date: Thu, 03 Aug 2023 13:24:38 +0200 [thread overview]
Message-ID: <87fs50nzbd.fsf@secure.mitica> (raw)
In-Reply-To: <9A87E859-3D80-40CC-923C-1B47243BD4C8@qti.qualcomm.com> (Mark Burton's message of "Thu, 3 Aug 2023 08:40:11 +0000")
Mark Burton <mburton@qti.qualcomm.com> wrote:
> Are too many people away right now?
Hi
Some of us are still working O:-)
But I think that the easiest way to cancel it is if nobody puts an
agenda.
Later, Juan.
prev parent reply other threads:[~2023-08-03 11:25 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-03 8:33 QEMU developers fortnightly conference for 2023-08-08 juan.quintela
2023-08-03 8:40 ` Mark Burton
2023-08-03 11:24 ` Juan Quintela [this message]
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=87fs50nzbd.fsf@secure.mitica \
--to=juan.quintela@gmail.com \
--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=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=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).