From: Markus Armbruster <armbru@redhat.com>
To: Alexander Graf <agraf@suse.de>
Cc: qemu list <qemu-devel@nongnu.org>,
KVM devel mailing list <kvm@vger.kernel.org>,
quintela@redhat.com
Subject: Re: [Qemu-devel] KVM call agenda for 2014-04-15
Date: Tue, 15 Apr 2014 18:56:34 +0200 [thread overview]
Message-ID: <87ob02a5vh.fsf@blackfin.pond.sub.org> (raw)
In-Reply-To: <534D4858.9040302@suse.de> (Alexander Graf's message of "Tue, 15 Apr 2014 16:55:20 +0200")
Alexander Graf <agraf@suse.de> writes:
> On 04/15/2014 04:00 PM, Markus Armbruster wrote:
>> Juan Quintela <quintela@redhat.com> writes:
>>
>>> Juan Quintela <quintela@redhat.com> wrote:
>>>> Hi
>>>>
>>>> Please, send any topic that you are interested in covering.
>>>>
>>>> Thanks, Juan.
>>> As there are no topics, no call.
>> Did we have a call anyway? IRC log looks like we did...
>
> Yes, we did. Whoever attended, please reply with things I mixed up or
> forgot.
>
> Two topics:
[...]
> 2) -device for non-PCI devices
Interesting stuff, hate to have missed it.
Can we please ensure more useful advance notice than "monitor the IRC
channel around call time"? Decide call / no call the night before would
work nicely for me.
next prev parent reply other threads:[~2014-04-15 16:56 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-14 17:37 KVM call agenda for 2014-04-15 Juan Quintela
2014-04-15 13:09 ` [Qemu-devel] " Alexander Graf
2014-04-15 13:26 ` Juan Quintela
2014-04-15 14:00 ` [Qemu-devel] " Markus Armbruster
2014-04-15 14:55 ` Alexander Graf
2014-04-15 15:32 ` [Qemu-devel] " Eric Auger
2014-04-16 10:48 ` Alexander Graf
2014-04-15 16:18 ` Peter Maydell
2014-04-15 16:56 ` Markus Armbruster [this message]
2014-04-15 21:34 ` Alexander Graf
2014-04-16 6:26 ` Markus Armbruster
2014-04-16 7:25 ` Alexander Graf
2014-04-15 16:09 ` 陈梁
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=87ob02a5vh.fsf@blackfin.pond.sub.org \
--to=armbru@redhat.com \
--cc=agraf@suse.de \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox