From: Gleb Natapov <gleb@qumranet.com>
To: Anthony Liguori <anthony@codemonkey.ws>
Cc: Blue Swirl <blauwirbel@gmail.com>, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH v5 0/8] Add new firmware configuration mechanism
Date: Wed, 10 Sep 2008 18:33:13 +0300 [thread overview]
Message-ID: <20080910153313.GI5924@minantech.com> (raw)
In-Reply-To: <48C7E7F7.2060600@codemonkey.ws>
On Wed, Sep 10, 2008 at 10:29:59AM -0500, Anthony Liguori wrote:
> Gleb Natapov wrote:
>> Hi,
>>
>> Here the latest version of the patch series. I hope now ready for inclusion.
>>
>
> Since Blue Swirl has been the most active in reviewing this series, I'm
> looking to him to decide when and to apply the series. AFAICT, it looks
> ready to go.
>
I'll send a new version soon with the latest Blue Swirl addition of
write support and different IO ports for control and data.
--
Gleb.
next prev parent reply other threads:[~2008-09-10 15:33 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-08 5:42 [Qemu-devel] [PATCH v5 0/8] Add new firmware configuration mechanism Gleb Natapov
2008-09-08 5:42 ` [Qemu-devel] [PATCH v5 1/8] Key/value based qemu<->guest firmware communication mechanism Gleb Natapov
2008-09-08 5:42 ` [Qemu-devel] [PATCH v5 2/8] Add -uuid command line option Gleb Natapov
2008-09-08 5:42 ` [Qemu-devel] [PATCH v5 3/8] Add "info uuid" command to monitor Gleb Natapov
2008-09-08 5:42 ` [Qemu-devel] [PATCH v5 4/8] Use libuuid if available Gleb Natapov
2008-09-08 5:42 ` [Qemu-devel] [PATCH v5 5/8] Add UUID to firmware configuration info Gleb Natapov
2008-09-08 5:42 ` [Qemu-devel] [PATCH v5 6/8] Pass cpu speed into SM BIOS Gleb Natapov
2008-09-08 5:42 ` [Qemu-devel] [PATCH v5 7/8] Add common keys to firmware configuration Gleb Natapov
2008-09-08 5:42 ` [Qemu-devel] [PATCH v5 8/8] Add sparc " Gleb Natapov
2008-09-10 15:29 ` [Qemu-devel] [PATCH v5 0/8] Add new firmware configuration mechanism Anthony Liguori
2008-09-10 15:33 ` Gleb Natapov [this message]
2008-09-10 16:34 ` Blue Swirl
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=20080910153313.GI5924@minantech.com \
--to=gleb@qumranet.com \
--cc=anthony@codemonkey.ws \
--cc=blauwirbel@gmail.com \
--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).