From: Paolo Bonzini <pbonzini@redhat.com>
To: "Gabriel L. Somlo" <gsomlo@gmail.com>,
Kevin O'Connor <kevin@koconnor.net>
Cc: seabios@seabios.org, qemu-devel@nongnu.org, agraf@suse.de
Subject: Re: [Qemu-devel] [SeaBIOS] [PATCH 1/2] SMBIOS: Update Type 17 (Memory Device) struct to v2.3
Date: Fri, 07 Feb 2014 16:37:58 +0100 [thread overview]
Message-ID: <52F4FDD6.8090606@redhat.com> (raw)
In-Reply-To: <20140206133825.GX29329@ERROL.INI.CMU.EDU>
Il 06/02/2014 14:38, Gabriel L. Somlo ha scritto:
> But anyhow, right now QEMU seems to be making relatively minor tweaks
> to something that's firmly at home in SeaBIOS, which is why I sent my
> patches to the latter...
Yeah, that's correct. There's really no particular hook in QEMU to do this.
Paolo
prev parent reply other threads:[~2014-02-07 15:38 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-04 19:02 [Qemu-devel] [PATCH 1/2] SMBIOS: Update Type 17 (Memory Device) struct to v2.3 Gabriel L. Somlo
2014-02-06 1:02 ` [Qemu-devel] [SeaBIOS] " Kevin O'Connor
2014-02-06 13:38 ` Gabriel L. Somlo
2014-02-07 15:37 ` Paolo Bonzini [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=52F4FDD6.8090606@redhat.com \
--to=pbonzini@redhat.com \
--cc=agraf@suse.de \
--cc=gsomlo@gmail.com \
--cc=kevin@koconnor.net \
--cc=qemu-devel@nongnu.org \
--cc=seabios@seabios.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).