From: Gerd Hoffmann <kraxel@redhat.com>
To: "Michael S. Tsirkin" <mst@redhat.com>
Cc: QEMU Developers <qemu-devel@nongnu.org>
Subject: [Qemu-devel] Re: [PATCH] eepro100: Update ROM file support
Date: Wed, 13 Jan 2010 13:14:28 +0100 [thread overview]
Message-ID: <4B4DB924.5000409@redhat.com> (raw)
In-Reply-To: <20100111183757.GA13725@redhat.com>
On 01/11/10 19:37, Michael S. Tsirkin wrote:
> On Thu, Jan 07, 2010 at 05:13:30PM +0100, Stefan Weil wrote:
>> Use new way to associate ROM files to devices.
Patch looks good to me.
>> Maybe it is even possible to create a single
>> pxe-i8255x.bin which supports all eepro100 devices
>> (not supported with current etherboot).
Would be nice indeed. Via .romfile we can easily handle any device ->
rom filename mapping though, so if this doesn't work out it isn't a big
issue too.
>>
>> Signed-off-by: Stefan Weil<weil@mail.berlios.de>
>
> Gerd, could you ack this patch please?
Acked-by: Gerd Hoffmann <kraxel@redhat.com>
cheers,
Gerd
prev parent reply other threads:[~2010-01-13 12:14 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-07 16:13 [Qemu-devel] [PATCH] eepro100: Update ROM file support Stefan Weil
2010-01-11 18:37 ` [Qemu-devel] " Michael S. Tsirkin
2010-01-13 12:14 ` 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=4B4DB924.5000409@redhat.com \
--to=kraxel@redhat.com \
--cc=mst@redhat.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).