From: Gerd Hoffmann <kraxel@redhat.com>
To: qemu-devel@nongnu.org
Cc: "Michael S. Tsirkin" <mst@redhat.com>,
"Gerd Hoffmann" <kraxel@redhat.com>,
"Philippe Mathieu-Daudé" <philmd@linaro.org>,
"Ani Sinha" <anisinha@redhat.com>,
"Igor Mammedov" <imammedo@redhat.com>
Subject: [PULL 0/8] Firmware/edk2 20230918 patches
Date: Mon, 18 Sep 2023 15:33:22 +0200 [thread overview]
Message-ID: <20230918133338.2399701-1-kraxel@redhat.com> (raw)
The following changes since commit c5ea91da443b458352c1b629b490ee6631775cb4:
Merge tag 'pull-trivial-patches' of https://gitlab.com/mjt0k/qemu into staging (2023-09-08 10:06:25 -0400)
are available in the Git repository at:
https://gitlab.com/kraxel/qemu.git tags/firmware/edk2-20230918-pull-request
for you to fetch changes up to 0ec0767e59261b7a1f59e904020cf52b45380e54:
tests/acpi: disallow virt/SSDT.memhp updates (2023-09-18 15:27:27 +0200)
----------------------------------------------------------------
edk2: update to edk2-stable202308
v2: include acpi test data updates
----------------------------------------------------------------
Gerd Hoffmann (8):
tests/acpi: allow virt/SSDT.memhp updates
edk2: update build script
edk2: update build config
edk2: workaround edk-stable202308 bug
edk2: update submodule to edk2-stable202308
edk2: update binaries to edk2-stable202308
tests/acpi: update virt/SSDT.memhp
tests/acpi: disallow virt/SSDT.memhp updates
roms/edk2-build.py | 202 ++++++++++++++++---------
pc-bios/edk2-aarch64-code.fd.bz2 | Bin 1508184 -> 1573561 bytes
pc-bios/edk2-arm-code.fd.bz2 | Bin 1483149 -> 1560966 bytes
pc-bios/edk2-i386-code.fd.bz2 | Bin 1695318 -> 1770410 bytes
pc-bios/edk2-i386-secure-code.fd.bz2 | Bin 1922002 -> 2121818 bytes
pc-bios/edk2-riscv-code.fd.bz2 | Bin 0 -> 1177402 bytes
pc-bios/edk2-riscv-vars.fd.bz2 | Bin 0 -> 231 bytes
pc-bios/edk2-riscv.fd.bz2 | Bin 1096418 -> 0 bytes
pc-bios/edk2-x86_64-code.fd.bz2 | Bin 1796544 -> 1887921 bytes
pc-bios/edk2-x86_64-microvm.fd.bz2 | Bin 1697788 -> 1782629 bytes
pc-bios/edk2-x86_64-secure-code.fd.bz2 | Bin 1999841 -> 2200701 bytes
roms/edk2 | 2 +-
roms/edk2-build.config | 12 +-
tests/data/acpi/virt/SSDT.memhp | Bin 1817 -> 1817 bytes
14 files changed, 139 insertions(+), 77 deletions(-)
create mode 100644 pc-bios/edk2-riscv-code.fd.bz2
create mode 100644 pc-bios/edk2-riscv-vars.fd.bz2
delete mode 100644 pc-bios/edk2-riscv.fd.bz2
--
2.41.0
next reply other threads:[~2023-09-18 13:36 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-18 13:33 Gerd Hoffmann [this message]
2023-09-18 13:33 ` [PULL 1/8] tests/acpi: allow virt/SSDT.memhp updates Gerd Hoffmann
2023-09-18 13:33 ` [PULL 2/8] edk2: update build script Gerd Hoffmann
2023-09-18 13:33 ` [PULL 3/8] edk2: update build config Gerd Hoffmann
2023-09-18 13:33 ` [PULL 4/8] edk2: workaround edk-stable202308 bug Gerd Hoffmann
2023-09-18 13:33 ` [PULL 5/8] edk2: update submodule to edk2-stable202308 Gerd Hoffmann
2023-09-18 13:33 ` [PULL 7/8] tests/acpi: update virt/SSDT.memhp Gerd Hoffmann
2023-09-18 13:33 ` [PULL 8/8] tests/acpi: disallow virt/SSDT.memhp updates Gerd Hoffmann
2023-09-19 19:13 ` [PULL 0/8] Firmware/edk2 20230918 patches Stefan Hajnoczi
2023-11-11 17:19 ` Akihiko Odaki
2023-11-13 11:09 ` Gerd Hoffmann
2023-11-17 16:00 ` Akihiko Odaki
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=20230918133338.2399701-1-kraxel@redhat.com \
--to=kraxel@redhat.com \
--cc=anisinha@redhat.com \
--cc=imammedo@redhat.com \
--cc=mst@redhat.com \
--cc=philmd@linaro.org \
--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).