qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Gerd Hoffmann <kraxel@redhat.com>
To: qemu-devel@nongnu.org
Cc: "Philippe Mathieu-Daudé" <philmd@linaro.org>,
	"Gerd Hoffmann" <kraxel@redhat.com>
Subject: [PULL 0/3] Edk2 stable202302 20230309 patches
Date: Thu,  9 Mar 2023 12:57:11 +0100	[thread overview]
Message-ID: <20230309115714.906369-1-kraxel@redhat.com> (raw)

The following changes since commit 9832009d9dd2386664c15cc70f6e6bfe062be8bd:

  Merge tag 'pull-riscv-to-apply-20230306' of https://gitlab.com/palmer-dabbelt/qemu into staging (2023-03-07 12:53:00 +0000)

are available in the Git repository at:

  https://gitlab.com/kraxel/qemu.git tags/edk2-stable202302-20230309-pull-request

for you to fetch changes up to 75bc97ac50634229fa9da45faa1fa64bbe6024c7:

  edk2: update firmware binaries (2023-03-09 12:49:29 +0100)

----------------------------------------------------------------
edk2: update to 202302 stable tag

----------------------------------------------------------------

Gerd Hoffmann (3):
  edk2: update submodule to edk2-stable202302
  edk2: replace build scripts
  edk2: update firmware binaries

 roms/edk2-build.py                     | 372 +++++++++++++++++++++++++
 pc-bios/edk2-aarch64-code.fd.bz2       | Bin 1161290 -> 1508803 bytes
 pc-bios/edk2-arm-code.fd.bz2           | Bin 1161845 -> 1482646 bytes
 pc-bios/edk2-i386-code.fd.bz2          | Bin 1282120 -> 1695318 bytes
 pc-bios/edk2-i386-secure-code.fd.bz2   | Bin 1473677 -> 1922002 bytes
 pc-bios/edk2-riscv.fd.bz2              | Bin 0 -> 1096510 bytes
 pc-bios/edk2-x86_64-code.fd.bz2        | Bin 1327522 -> 1796544 bytes
 pc-bios/edk2-x86_64-microvm.fd.bz2     | Bin 1309407 -> 1697788 bytes
 pc-bios/edk2-x86_64-secure-code.fd.bz2 | Bin 1513711 -> 1999841 bytes
 roms/Makefile                          |  29 +-
 roms/Makefile.edk2                     | 178 ------------
 roms/edk2                              |   2 +-
 roms/edk2-build.config                 | 119 ++++++++
 roms/edk2-build.sh                     |  55 ----
 roms/edk2-funcs.sh                     | 273 ------------------
 15 files changed, 499 insertions(+), 529 deletions(-)
 create mode 100755 roms/edk2-build.py
 create mode 100644 pc-bios/edk2-riscv.fd.bz2
 delete mode 100644 roms/Makefile.edk2
 create mode 100644 roms/edk2-build.config
 delete mode 100755 roms/edk2-build.sh
 delete mode 100644 roms/edk2-funcs.sh

-- 
2.39.2



             reply	other threads:[~2023-03-09 11:58 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-09 11:57 Gerd Hoffmann [this message]
2023-03-09 11:57 ` [PULL 1/3] edk2: update submodule to edk2-stable202302 Gerd Hoffmann
2023-03-09 11:57 ` [PULL 2/3] edk2: replace build scripts Gerd Hoffmann
2023-03-10 13:58   ` Simon Glass
2023-03-15 15:49     ` Gerd Hoffmann
2023-03-20 19:19       ` Simon Glass
2023-03-09 11:57 ` [PULL 3/3] edk2: update firmware binaries Gerd Hoffmann
2023-03-09 22:09   ` Simon Glass
2023-03-10  6:37     ` Gerd Hoffmann
2023-03-10 21:00       ` Simon Glass
2023-03-10 11:30 ` [PULL 0/3] Edk2 stable202302 20230309 patches Peter Maydell
2023-03-10 13:09   ` Philippe Mathieu-Daudé
2023-03-15 15:56   ` Gerd Hoffmann
2023-03-15 16:16     ` Laszlo Ersek
2023-03-16  7:55       ` Gerd Hoffmann
2023-03-10 13:18 ` Philippe Mathieu-Daudé

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=20230309115714.906369-1-kraxel@redhat.com \
    --to=kraxel@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).