From: "Alex Bennée" <alex.bennee@linaro.org>
To: qemu-devel <qemu-devel@nongnu.org>
Cc: "Markus Armbruster" <armbru@redhat.com>,
"Philippe Mathieu-Daudé" <philmd@linaro.org>,
"Mark Burton" <mburton@qti.qualcomm.com>
Subject: KVM/QEMU Community Call 6th Feb Agenda Items
Date: Fri, 02 Feb 2024 15:55:17 +0000 [thread overview]
Message-ID: <87mssij1y2.fsf@draig.linaro.org> (raw)
Hi,
The KVM/QEMU community call is at:
https://meet.jit.si/kvmcallmeeting
@
6/2/2024 14:00 UTC
As I'll be away Philippe has volunteered to run the meeting.
So far we have one agenda item which is to discuss next steps from
Markus' post about dynamic modelling:
Message-ID: <87o7d1i7ky.fsf@pond.sub.org>
Date: Wed, 31 Jan 2024 21:14:21 +0100
Subject: Dynamic & heterogeneous machines, initial configuration: problems
If there are any other agenda items you would like to discuss then
please respond to this email.
--
Alex Bennée
Virtualisation Tech Lead @ Linaro
next reply other threads:[~2024-02-02 15:56 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-02 15:55 Alex Bennée [this message]
2024-02-09 21:12 ` KVM/QEMU Community Call 6th Feb Agenda Items (minutes) Philippe Mathieu-Daudé
2024-02-09 21:15 ` KVM/QEMU Community Call 6th Feb Agenda Items 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=87mssij1y2.fsf@draig.linaro.org \
--to=alex.bennee@linaro.org \
--cc=armbru@redhat.com \
--cc=mburton@qti.qualcomm.com \
--cc=philmd@linaro.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).