From: Juan Quintela <quintela@redhat.com>
To: qemu-devel <qemu-devel@nongnu.org>,
kvm-devel <kvm@vger.kernel.org>,
"Philippe Mathieu-Daudé" <f4bug@amsat.org>,
"Alex Bennée" <alex.bennee@linaro.org>
Subject: KVM call for agenda for 2023-03-21
Date: Sat, 18 Mar 2023 18:59:28 +0100 [thread overview]
Message-ID: <87zg8aj5z3.fsf@secure.mitica> (raw)
Hi
NOTE, NOTE, NOTE
Remember that we are back in that crazy part of the year when daylight
saving applies. Call is done on US timezone. If you are anything else,
just doublecheck that it is working for you properly.
NOTE, NOTE, NOTE
Topics in the backburner:
- single qemu binary
Philippe?
- The future of icount.
Alex? My understanding is that you are interested in
qemu 8.1 to open.
Anything else?
Please, send any topic that you are interested in covering.
At the end of Monday I will send an email with the agenda or the
cancellation of the call, so hurry up.
After discussions on the QEMU Summit, we are going to have always open a
KVM call where you can add topics.
Call details:
By popular demand, a google calendar public entry with it
https://calendar.google.com/calendar/event?action=TEMPLATE&tmeid=NWR0NWppODdqNXFyYzAwbzYza3RxN2dob3VfMjAyMjEwMThUMTMwMDAwWiBlZ2VkN2NraTA1bG11MXRuZ3ZrbDN0aGlkc0Bn&tmsrc=eged7cki05lmu1tngvkl3thids%40group.calendar.google.com&scp=ALL
(Let me know if you have any problems with the calendar entry. I just
gave up about getting right at the same time CEST, CET, EDT and DST).
If you need phone number details, contact me privately
Thanks, Juan.
next reply other threads:[~2023-03-18 18:00 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-18 17:59 Juan Quintela [this message]
2023-03-20 15:47 ` KVM call for agenda for 2023-03-21 Philippe Mathieu-Daudé
2023-03-20 21:49 ` Mark Cave-Ayland
2023-03-20 22:45 ` Bernhard Beschow
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=87zg8aj5z3.fsf@secure.mitica \
--to=quintela@redhat.com \
--cc=alex.bennee@linaro.org \
--cc=f4bug@amsat.org \
--cc=kvm@vger.kernel.org \
--cc=qemu-devel@nongnu.org \
/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).