From: Laszlo Ersek <lersek@redhat.com>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] [PULL 0/6] update edk2 submodule & binaries to edk2-stable201905
Date: Fri, 14 Jun 2019 22:23:27 +0200 [thread overview]
Message-ID: <20190614202333.19355-1-lersek@redhat.com> (raw)
The following changes since commit f3d0bec9f80e4ed7796fffa834ba0a53f2094f7f:
Merge remote-tracking branch 'remotes/maxreitz/tags/pull-block-2019-06-14' into staging (2019-06-14 14:46:13 +0100)
are available in the Git repository at:
https://github.com/lersek/qemu.git tags/edk2-pull-2019-06-14
for you to fetch changes up to 541617cad3445fdc6735e9e5752e1f698e337737:
pc-bios: update the README file with edk2-stable201905 information (2019-06-14 21:48:00 +0200)
----------------------------------------------------------------
edk2-stable201905 was released on 2019-06-06:
https://github.com/tianocore/edk2/releases/tag/edk2-stable201905
Advance QEMU's edk2 submodule to edk2-stable201905, and rebuild the
firmware binaries. This should be the edk2 release that goes into QEMU
4.1.
Launchpad: https://bugs.launchpad.net/qemu/+bug/1831477
----------------------------------------------------------------
Laszlo Ersek (6):
roms/Makefile.edk2: define edk2-stable201905 network feature test macros
roms/edk2: update submodule from edk2-stable201903 to edk2-stable201905
roms/Makefile.edk2: remove edk2-stable201903 network feature test macros
roms/Makefile.edk2: update input file list for "pc-bios/edk2-licenses.txt"
pc-bios: refresh edk2 build artifacts for edk2-stable201905
pc-bios: update the README file with edk2-stable201905 information
pc-bios/README | 14 +-
pc-bios/edk2-aarch64-code.fd.bz2 | Bin 1177603 -> 1178070 bytes
pc-bios/edk2-arm-code.fd.bz2 | Bin 1173662 -> 1172752 bytes
pc-bios/edk2-i386-code.fd.bz2 | Bin 1688659 -> 1736199 bytes
pc-bios/edk2-i386-secure-code.fd.bz2 | Bin 1881979 -> 1943949 bytes
pc-bios/edk2-licenses.txt | 752 ++++++++++++++++++++++++++++++---
pc-bios/edk2-x86_64-code.fd.bz2 | Bin 1669280 -> 1717094 bytes
pc-bios/edk2-x86_64-secure-code.fd.bz2 | Bin 1901210 -> 1958037 bytes
roms/Makefile.edk2 | 22 +-
roms/edk2 | 2 +-
10 files changed, 714 insertions(+), 76 deletions(-)
--
2.19.1.3.g30247aa5d201
next reply other threads:[~2019-06-14 20:25 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-14 20:23 Laszlo Ersek [this message]
2019-06-14 20:23 ` [Qemu-devel] [PULL 1/6] roms/Makefile.edk2: define edk2-stable201905 network feature test macros Laszlo Ersek
2019-06-14 20:23 ` [Qemu-devel] [PULL 2/6] roms/edk2: update submodule from edk2-stable201903 to edk2-stable201905 Laszlo Ersek
2019-06-14 20:23 ` [Qemu-devel] [PULL 3/6] roms/Makefile.edk2: remove edk2-stable201903 network feature test macros Laszlo Ersek
2019-06-14 20:23 ` [Qemu-devel] [PULL 4/6] roms/Makefile.edk2: update input file list for "pc-bios/edk2-licenses.txt" Laszlo Ersek
2019-06-14 20:23 ` [Qemu-devel] [PULL 5/6] pc-bios: refresh edk2 build artifacts for edk2-stable201905 Laszlo Ersek
2019-06-14 20:23 ` [Qemu-devel] [PULL 6/6] pc-bios: update the README file with edk2-stable201905 information Laszlo Ersek
2019-06-17 10:54 ` [Qemu-devel] [PULL 0/6] update edk2 submodule & binaries to edk2-stable201905 Peter Maydell
2019-06-19 23:40 ` Laszlo Ersek
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=20190614202333.19355-1-lersek@redhat.com \
--to=lersek@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).