All of lore.kernel.org
 help / color / mirror / Atom feed
From: Anthony Liguori <anthony@codemonkey.ws>
To: Markus Armbruster <armbru@redhat.com>
Cc: Anthony Liguori <anthony@codemonkey.ws>,
	Chris Wright <chrisw@redhat.com>,
	qemu-devel@nongnu.org, kvm@vger.kernel.org
Subject: Re: [Qemu-devel] KVM call agenda for Feb 15
Date: Tue, 15 Feb 2011 08:00:01 -0600	[thread overview]
Message-ID: <4D5A86E1.1000801@codemonkey.ws> (raw)
In-Reply-To: <m3lj1hfqfz.fsf@blackfin.pond.sub.org>

On 02/15/2011 06:11 AM, Markus Armbruster wrote:
> Anthony Liguori<anthony@codemonkey.ws>  writes:
>
>    
>> On 02/14/2011 11:56 AM, Chris Wright wrote:
>>      
>>> Please send in any agenda items you are interested in covering.
>>>
>>>        
>> - QAPI and QMP events
>> - qdev future
>>      
>      Do we need a qdev tree and a maintainer for it?
>    

I think we need a clear design and direction first.

Regards,

Anthony Liguori

>> I don't really have a coherent plan for the second one yet so let's
>> just discuss this as time permits.
>>      
>    


WARNING: multiple messages have this Message-ID (diff)
From: Anthony Liguori <anthony@codemonkey.ws>
To: Markus Armbruster <armbru@redhat.com>
Cc: Chris Wright <chrisw@redhat.com>,
	qemu-devel@nongnu.org, kvm@vger.kernel.org
Subject: Re: [Qemu-devel] KVM call agenda for Feb 15
Date: Tue, 15 Feb 2011 08:00:01 -0600	[thread overview]
Message-ID: <4D5A86E1.1000801@codemonkey.ws> (raw)
In-Reply-To: <m3lj1hfqfz.fsf@blackfin.pond.sub.org>

On 02/15/2011 06:11 AM, Markus Armbruster wrote:
> Anthony Liguori<anthony@codemonkey.ws>  writes:
>
>    
>> On 02/14/2011 11:56 AM, Chris Wright wrote:
>>      
>>> Please send in any agenda items you are interested in covering.
>>>
>>>        
>> - QAPI and QMP events
>> - qdev future
>>      
>      Do we need a qdev tree and a maintainer for it?
>    

I think we need a clear design and direction first.

Regards,

Anthony Liguori

>> I don't really have a coherent plan for the second one yet so let's
>> just discuss this as time permits.
>>      
>    

  reply	other threads:[~2011-02-15 14:00 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-02-14 17:56 KVM call agenda for Feb 15 Chris Wright
2011-02-14 17:56 ` [Qemu-devel] " Chris Wright
2011-02-14 19:54 ` Anthony Liguori
2011-02-14 19:54   ` Anthony Liguori
2011-02-15 12:11   ` Markus Armbruster
2011-02-15 14:00     ` Anthony Liguori [this message]
2011-02-15 14:00       ` Anthony Liguori
2011-02-15 13:42   ` Gleb Natapov
2011-02-15 13:42     ` Gleb Natapov
2011-02-14 22:18 ` Anthony Liguori
2011-02-14 22:18   ` Anthony Liguori
2011-02-15 10:37   ` Amit Shah
2011-02-15 10:44   ` Avi Kivity
2011-02-15 10:44     ` Avi Kivity
2011-02-15 13:58     ` Anthony Liguori
2011-02-15 14:03       ` Avi Kivity
2011-02-15 16:03   ` Stefan Hajnoczi
2011-02-15 16:03     ` Stefan Hajnoczi

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=4D5A86E1.1000801@codemonkey.ws \
    --to=anthony@codemonkey.ws \
    --cc=armbru@redhat.com \
    --cc=chrisw@redhat.com \
    --cc=kvm@vger.kernel.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 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.