qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Gerd Hoffmann <kraxel@redhat.com>
To: Anthony Liguori <anthony@codemonkey.ws>
Cc: "qemu-devel@nongnu.org" <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] qdev merge plans?
Date: Wed, 15 Jul 2009 08:21:34 +0200	[thread overview]
Message-ID: <4A5D756E.6030101@redhat.com> (raw)
In-Reply-To: <4A5D05D0.4030004@codemonkey.ws>

On 07/15/09 00:25, Anthony Liguori wrote:
> Gerd Hoffmann wrote:
>> Hi Anthony,
>>
>> Your queue continues bitrotting. BlueSwirl did more qdev conversions
>> with the result that more fixups are needed to make the tree build
>> again once your queue is pushed ...
>>
>> For now I did incremental fixups and didn't change the patches you
>> have queued up already. At least for the build failure this isn't
>> ideal though as it leaves a few revisions which don't build which is
>> bad for bisecting.
>>
>> So what is your plan to handle the mess^H^H^H^Hmerge?
>
> Early in your series, you introduce -device. But -device syntax doesn't
> seem to be resolved yet.

The patch sits in your queue nevertheless, so I'm not sure what your 
plan is ...

> I don't think it's appropriate to pull in -device this close to the
> feature freeze when the command line syntax is still being debated. You
> only countered Paul's suggestions this morning so I don't think there's
> any indication that this discussion has converged yet.

Ok, so it sounds like you'll plan to drop the patch(es) from the queue. 
  Ok.  I'll go post fresh patch series based on upstream/master then, so 
you can replace the qdev bits in your queue.

> Quite a lot of your queue consists of things you've only posted as
> Proof-of-concept series (like qdev/isa).

Yes, as mentioned there are quite a few work-in-progress patches.

> So let me ask you, what is the set of patches that you think is
> non-contended, posted as a non-RFC, but not yet merged?

I'll sort and repost the patches today.  Rough plan is:

(1) Split the patch series in your queue into two:
     - One with the properties bits (should be ready to merge).
     - One with the -device stuff (for further discussion
       and maybe merge).
(2) Repost qdev/compat bits, slightly updated according to
     review comments (should be ready to merge too).

cheers,
   Gerd

      reply	other threads:[~2009-07-15  6:21 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-07-14 21:48 [Qemu-devel] qdev merge plans? Gerd Hoffmann
2009-07-14 22:25 ` Anthony Liguori
2009-07-15  6:21   ` Gerd Hoffmann [this message]

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=4A5D756E.6030101@redhat.com \
    --to=kraxel@redhat.com \
    --cc=anthony@codemonkey.ws \
    --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 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).