From: Stefano Stabellini <stefano.stabellini@eu.citrix.com>
To: Anthony Liguori <anthony@codemonkey.ws>
Cc: "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>,
Gerd Hoffmann <kraxel@redhat.com>,
"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>
Subject: Re: [Xen-devel] Re: [Qemu-devel] [PATCH 00/10] xen: pv domain support.
Date: Wed, 22 Apr 2009 17:54:35 +0100 [thread overview]
Message-ID: <49EF4BCB.5020301@eu.citrix.com> (raw)
In-Reply-To: <49EF3D28.50003@codemonkey.ws>
Anthony Liguori wrote:
> Gerd Hoffmann wrote:
>> Hi,
>>
>> Next round, addressing review comments:
>>
>> * Fixup more "if (-1 == foo()) bar()" compare style.
>> * Fixup logging: kill fprintf(stderr, ...), use logging API.
>> * Kill some unneeded malloc failure checks.
>>
>> The patches are also rebased to latest git and got a few adaptions to
>> recent cha
>>
>
> Applied full series. Thanks.
>
> I think it can still use some love (some files missing
> copyrights/license, for instance), but it's all extremely well contained
> so there's little point in keeping it out of tree.
>
The point was for Ian to be able to pull directly from qemu without
getting any conflicts on those files.
To be honest they are fairly similar now, so I am confident that git
will be able to do its magic.
next prev parent reply other threads:[~2009-04-22 16:54 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-21 12:19 [Qemu-devel] [PATCH 00/10] xen: pv domain support Gerd Hoffmann
2009-04-21 12:19 ` [Qemu-devel] [PATCH 01/10] xen: groundwork for xen support Gerd Hoffmann
2009-04-21 12:20 ` [Qemu-devel] [PATCH 02/10] xen: backend driver core Gerd Hoffmann
2009-04-21 12:20 ` [Qemu-devel] [PATCH 03/10] xen: add console backend driver Gerd Hoffmann
2009-04-21 15:46 ` Blue Swirl
2009-04-21 12:20 ` [Qemu-devel] [PATCH 04/10] xen: add framebuffer " Gerd Hoffmann
2009-04-21 12:20 ` [Qemu-devel] [PATCH 05/10] xen: add block device " Gerd Hoffmann
2009-04-21 15:47 ` Blue Swirl
2009-04-21 12:20 ` [Qemu-devel] [PATCH 06/10] xen: add net " Gerd Hoffmann
2009-04-21 12:20 ` [Qemu-devel] [PATCH 07/10] xen: blk & nic configuration via cmd line Gerd Hoffmann
2009-04-21 12:20 ` [Qemu-devel] [PATCH 08/10] xen: pv domain builder Gerd Hoffmann
2009-04-21 15:48 ` Blue Swirl
2009-04-21 12:20 ` [Qemu-devel] [PATCH 09/10] simplify vga selection Gerd Hoffmann
2009-04-21 12:20 ` [Qemu-devel] [PATCH 10/10] xen: add -vga xenfb option, configure xenfb Gerd Hoffmann
2009-04-21 15:25 ` [Qemu-devel] Re: [Xen-devel] [PATCH 00/10] xen: pv domain support Ian Jackson
2009-04-21 16:16 ` Gerd Hoffmann
2009-05-19 10:54 ` Mark Johnson
2009-05-19 16:04 ` Ian Jackson
2009-04-22 15:52 ` [Qemu-devel] " Anthony Liguori
2009-04-22 16:54 ` Stefano Stabellini [this message]
2009-04-23 9:55 ` [Xen-devel] " Gerd Hoffmann
-- strict thread matches above, loose matches on Subject: below --
2009-04-01 21:39 Gerd Hoffmann
2009-04-02 21:14 ` Laurent Vivier
2009-04-03 20:24 ` Gerd Hoffmann
2009-04-03 23:04 ` Alexander Graf
2009-04-05 8:48 ` Avi Kivity
2009-04-05 11:17 ` Alexander Graf
2009-04-05 11:37 ` Avi Kivity
2009-04-06 13:56 ` [Xen-devel] " Stefano Stabellini
2009-04-06 6:53 ` Gerd Hoffmann
2009-04-06 20:44 ` [Xen-devel] " Jeremy Fitzhardinge
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=49EF4BCB.5020301@eu.citrix.com \
--to=stefano.stabellini@eu.citrix.com \
--cc=anthony@codemonkey.ws \
--cc=kraxel@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=xen-devel@lists.xensource.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).