From: "Michael S. Tsirkin" <mst@redhat.com>
To: Juan Quintela <quintela@redhat.com>
Cc: KVM devel mailing list <kvm@vger.kernel.org>,
qemu-devel qemu-devel <qemu-devel@nongnu.org>
Subject: KVM call agenda for 2014-02-17 (was Re: KVM call agenda for 2014-02-04)
Date: Mon, 17 Feb 2014 16:19:43 +0200 [thread overview]
Message-ID: <20140217141943.GA22799@redhat.com> (raw)
In-Reply-To: <87k3dcfj6p.fsf@elfo.mitica>
On Mon, Feb 03, 2014 at 01:57:02PM +0100, Juan Quintela wrote:
> Hi
>
> Please, send any topic that you are interested in covering.
>
> * Should we change anything to get more people to sign for the call?
> There hasn't been a call in quite a long time. Ideas?
>
> Thanks, Juan.
>
> Call details:
>
> 09:00 AM to 10:00 AM EDT
> Every two weeks
>
> If you need phone number details, contact me privately
How about discussing plans for x2apic?
next prev parent reply other threads:[~2014-02-17 14:14 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-03 12:57 KVM call agenda for 2014-02-04 Juan Quintela
2014-02-04 13:53 ` Juan Quintela
2014-02-17 14:19 ` Michael S. Tsirkin [this message]
2014-02-17 14:17 ` [Qemu-devel] KVM call agenda for 2014-02-17 (was Re: KVM call agenda for 2014-02-04) Peter Maydell
2014-02-17 14:27 ` Michael S. Tsirkin
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=20140217141943.GA22799@redhat.com \
--to=mst@redhat.com \
--cc=kvm@vger.kernel.org \
--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.