From: Christian Borntraeger <borntraeger@de.ibm.com>
To: quintela@redhat.com,
qemu-develQEMU Developer <qemu-devel@nongnu.org>,
KVM devel mailing list <kvm@vger.kernel.org>
Cc: "Bharata B Rao" <bharata@linux.vnet.ibm.com>,
"Andreas Färber" <afaerber@suse.de>,
"David Gibson" <david@gibson.dropbear.id.au>,
"Matthew Rosato" <mjrosato@linux.vnet.ibm.com>,
"David Hildenbrand" <dahi@linux.vnet.ibm.com>
Subject: Re: KVH call for agenda for 2016-02-16
Date: Wed, 10 Feb 2016 16:48:06 +0100 [thread overview]
Message-ID: <56BB5BB6.8030301@de.ibm.com> (raw)
In-Reply-To: <871t8kpo6j.fsf@emacs.mitica>
On 02/10/2016 04:42 PM, Juan Quintela wrote:
>
>
> Hi
>
> 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://www.google.com/calendar/embed?src=dG9iMXRqcXAzN3Y4ZXZwNzRoMHE4a3BqcXNAZ3JvdXAuY2FsZW5kYXIuZ29vZ2xlLmNvbQ
>
> (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.
Since we seem to be stuck, I propose CPU hotplug as agenda item.
next prev parent reply other threads:[~2016-02-10 15:48 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-10 15:42 KVH call for agenda for 2016-02-16 Juan Quintela
2016-02-10 15:48 ` Christian Borntraeger [this message]
2016-02-12 17:28 ` Andreas Färber
2016-02-16 11:54 ` KVM " Christian Borntraeger
2016-02-17 20:40 ` Eduardo Habkost
2016-02-17 22:51 ` Juan Quintela
2016-02-22 19:02 ` [Qemu-devel] " Thomas Huth
2016-02-23 9:59 ` Juan Quintela
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=56BB5BB6.8030301@de.ibm.com \
--to=borntraeger@de.ibm.com \
--cc=afaerber@suse.de \
--cc=bharata@linux.vnet.ibm.com \
--cc=dahi@linux.vnet.ibm.com \
--cc=david@gibson.dropbear.id.au \
--cc=kvm@vger.kernel.org \
--cc=mjrosato@linux.vnet.ibm.com \
--cc=qemu-devel@nongnu.org \
--cc=quintela@redhat.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.