From: Christian Borntraeger <borntraeger@de.ibm.com>
To: Thomas Huth <thuth@redhat.com>,
quintela@redhat.com, KVM devel mailing list <kvm@vger.kernel.org>,
QEMU Developer <qemu-devel@nongnu.org>
Cc: pkrempa@redhat.com, "Eduardo Habkost" <ehabkost@redhat.com>,
"Bharata B Rao" <bharata@linux.vnet.ibm.com>,
"Igor Mammedov" <imammedo@redhat.com>,
"David Gibson" <dgibson@redhat.com>,
"Andreas Färber" <afaerber@suse.de>
Subject: Re: [Qemu-devel] KVM call for agenda for 2016-03-01
Date: Tue, 1 Mar 2016 14:56:22 +0100 [thread overview]
Message-ID: <56D59F86.2070707@de.ibm.com> (raw)
In-Reply-To: <56CEBE02.6090200@redhat.com>
On 02/25/2016 09:40 AM, Thomas Huth wrote:
> On 23.02.2016 16:33, 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.
>
> Shall we talk about CPU hotplug again? There are a lot of discussions
> going on, but as far as I can tell, it seems there is still no 100%
> common understanding yet how the final solution should really look like...
>
> Thomas
Hmpf. I have seen this too late. Can you cc some s390 folks the next time?
WARNING: multiple messages have this Message-ID (diff)
From: Christian Borntraeger <borntraeger@de.ibm.com>
To: Thomas Huth <thuth@redhat.com>,
quintela@redhat.com, KVM devel mailing list <kvm@vger.kernel.org>,
QEMU Developer <qemu-devel@nongnu.org>
Cc: pkrempa@redhat.com, "Eduardo Habkost" <ehabkost@redhat.com>,
"Bharata B Rao" <bharata@linux.vnet.ibm.com>,
"David Gibson" <dgibson@redhat.com>,
"Igor Mammedov" <imammedo@redhat.com>,
"Andreas Färber" <afaerber@suse.de>
Subject: Re: [Qemu-devel] KVM call for agenda for 2016-03-01
Date: Tue, 1 Mar 2016 14:56:22 +0100 [thread overview]
Message-ID: <56D59F86.2070707@de.ibm.com> (raw)
In-Reply-To: <56CEBE02.6090200@redhat.com>
On 02/25/2016 09:40 AM, Thomas Huth wrote:
> On 23.02.2016 16:33, 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.
>
> Shall we talk about CPU hotplug again? There are a lot of discussions
> going on, but as far as I can tell, it seems there is still no 100%
> common understanding yet how the final solution should really look like...
>
> Thomas
Hmpf. I have seen this too late. Can you cc some s390 folks the next time?
next prev parent reply other threads:[~2016-03-01 13:56 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-23 15:33 KVM call for agenda for 2016-03-01 Juan Quintela
2016-02-23 15:33 ` [Qemu-devel] " Juan Quintela
2016-02-25 8:40 ` Thomas Huth
2016-02-25 8:40 ` [Qemu-devel] " Thomas Huth
2016-02-25 12:47 ` Peter Krempa
2016-02-25 12:47 ` [Qemu-devel] " Peter Krempa
2016-02-25 17:19 ` Eduardo Habkost
2016-02-25 17:19 ` [Qemu-devel] " Eduardo Habkost
2016-03-01 13:56 ` Christian Borntraeger [this message]
2016-03-01 13:56 ` Christian Borntraeger
2016-03-01 13:49 ` Juan Quintela
2016-03-01 13:49 ` [Qemu-devel] " 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=56D59F86.2070707@de.ibm.com \
--to=borntraeger@de.ibm.com \
--cc=afaerber@suse.de \
--cc=bharata@linux.vnet.ibm.com \
--cc=dgibson@redhat.com \
--cc=ehabkost@redhat.com \
--cc=imammedo@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=pkrempa@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=quintela@redhat.com \
--cc=thuth@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.