From: Gerd Hoffmann <kraxel@redhat.com>
To: "seabios@seabios.org" <seabios@seabios.org>
Cc: Alex Williamson <alex.williamson@redhat.com>,
Kevin O'Connor <kevin@koconnor.net>,
"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>,
"Michael S. Tsirkin" <mst@redhat.com>
Subject: [Qemu-devel] 1.7.3.1 release planned
Date: Thu, 08 Aug 2013 15:43:48 +0200 [thread overview]
Message-ID: <5203A094.40100@redhat.com> (raw)
Hi,
I've just created a 1.7.3-stable branch. It has a single commit right
now, which is 2a9aeabdfb34374ecac25e7a8d21c9e368618cd4 from master
cherry-picked (Fix USB EHCI detection that was broken in hlist
conversion of PCIDevices).
My plan is to tag 1.7.3.1 next monday, so the update can be included in
qemu 1.6-rc3 planned for next monday.
Are there more patches which should go into the 1.7.3.1 bugfix release?
Commit ed88f6515c18d9520efa4a41ccb70038dfbe43f9 (acpi: sync FADT flags
from PIIX4 to Q35vga) looks like a candidate to me. Michael?
Also commit 1a113e1144113348e04cbe39fa81a448049e82a0 (Fix bug in CBFS
file walking with compressed files). Kevin?
cheers,
Gerd
next reply other threads:[~2013-08-08 13:44 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-08 13:43 Gerd Hoffmann [this message]
2013-08-08 14:07 ` [Qemu-devel] 1.7.3.1 release planned Michael S. Tsirkin
2013-08-09 3:36 ` Kevin O'Connor
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=5203A094.40100@redhat.com \
--to=kraxel@redhat.com \
--cc=alex.williamson@redhat.com \
--cc=kevin@koconnor.net \
--cc=mst@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).