From: Gerd Hoffmann <kraxel@redhat.com>
To: qemu-devel@nongnu.org
Cc: seabios@seabios.org, Gerd Hoffmann <kraxel@redhat.com>
Subject: [Qemu-devel] [PULL for-1.2] update seabios to 1.7.1
Date: Mon, 3 Sep 2012 17:21:17 +0200 [thread overview]
Message-ID: <1346685678-18644-1-git-send-email-kraxel@redhat.com> (raw)
Hi,
This pull updates seabios to the 1.7.1 version just released. The diff
to the snapshot merged is only two patches, and the kind of patches
(iasl buildfix, AMD PCscsi driver) can hardly cause regressions. It's
also nicer to ship a release instead of a git snapshot, so I strongly
suggest to update for the qemu 1.2 release.
please pull,
Gerd
are available in the git repository at:
git://git.kraxel.org/qemu seabios-1.7.1
Gerd Hoffmann (1):
seabios: update to release 1.7.1
pc-bios/bios.bin | Bin 131072 -> 131072 bytes
roms/seabios | 2 +-
2 files changed, 1 insertions(+), 1 deletions(-)
next reply other threads:[~2012-09-03 15:21 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-03 15:21 Gerd Hoffmann [this message]
2012-09-03 15:21 ` [Qemu-devel] [PATCH for-1.2] seabios: update to release 1.7.1 Gerd Hoffmann
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=1346685678-18644-1-git-send-email-kraxel@redhat.com \
--to=kraxel@redhat.com \
--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).