qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Paolo Bonzini <pbonzini@redhat.com>
To: "Andreas Färber" <afaerber@suse.de>
Cc: Developers qemu-devel <qemu-devel@nongnu.org>,
	KVM devel mailing list <kvm@vger.kernel.org>,
	quintela@redhat.com
Subject: Re: [Qemu-devel] KVM call agenda for Tuesday 7
Date: Tue, 07 Feb 2012 14:52:10 +0100	[thread overview]
Message-ID: <4F312C8A.9080700@redhat.com> (raw)
In-Reply-To: <4F312AFC.6020908@suse.de>

On 02/07/2012 02:45 PM, Andreas Färber wrote:
> Another topic that can be answered by email is what the time planning
> for the 4th QOM series looks like. Are there things that developers of
> new devices should keep in mind / start doing differently wrt SysBus?

Another related question is, should the 4th QOM series present a full 
composition tree based on the legacy qdev bus concept?  Currently it 
doesn't, but if not, why not?  That would help _a lot_ with removing 
PROP_PTR.

Paolo

  reply	other threads:[~2012-02-07 13:52 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-02-06 19:25 [Qemu-devel] KVM call agenda for Tuesday 7 Juan Quintela
2012-02-07 13:45 ` Andreas Färber
2012-02-07 13:52   ` Paolo Bonzini [this message]
2012-02-07 14:56     ` Anthony Liguori
2012-02-07 15:21       ` Paolo Bonzini
2012-02-07 16:24         ` Anthony Liguori
2012-02-07 16:27           ` Paolo Bonzini
2012-02-07 16:33             ` Anthony Liguori
2012-02-07 16:40               ` Peter Maydell
2012-02-07 17:04               ` Paolo Bonzini
2012-02-07 16:41         ` Andreas Färber
2012-02-07 16:53           ` Anthony Liguori
2012-02-07 18:01   ` Anthony Liguori
2012-02-07 18:17     ` Andreas Färber
2012-02-07 19:06       ` Anthony Liguori
2012-02-07 14:23 ` 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=4F312C8A.9080700@redhat.com \
    --to=pbonzini@redhat.com \
    --cc=afaerber@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;
as well as URLs for NNTP newsgroup(s).