On Thu, 11 Jan 2024 at 14:01, Gerd Hoffmann <kra...@redhat.com> wrote: > > On Wed, Dec 13, 2023 at 11:50:12AM +0100, Gerd Hoffmann wrote: > > The following changes since commit 9c74490bff6c8886a922008d0c9ce6cae70dd17e: > > > > Update version for v8.2.0-rc3 release (2023-12-06 14:34:20 -0500) > > > > are available in the Git repository at: > > > > https://gitlab.com/kraxel/qemu.git > > tags/firmware/edk2-20231213-pull-request > > > > for you to fetch changes up to 704f7cad5105246822686f65765ab92045f71a3b: > > > > tests/acpi: disallow tests/data/acpi/virt/SSDT.memhp changes (2023-12-13 > > 11:23:11 +0100) > > > > ---------------------------------------------------------------- > > edk2: update to git snapshot (maybe for-8.2) > > > > This updates edk2 to git master as of today. This picks up a patch > > (merged only yesterday, that's why this last-minute PR) which allows to > > work around a bug in shim, and enables that workaround in the qemu > > firmware builds. > > > > This solves a real-world problem on arm hardware, walk over to > > https://gitlab.com/qemu-project/qemu/-/issues/1990 to see the details. > > > > Merging this firmware update that close to the 8.2 release clearly is > > not without risks. If I get a 'no', I'm not going to complain. > > > > That said I'm not aware of any bugs, and landing this in 8.2.0 would > > make a bunch of folks hanging around in issue 1990 very happy. > > > > Alternative plan would be to merge this after the release, give it some > > time for testing, and assuming everything goes well schedule a backport > > for 8.2.1 > > Ping. > > As expected this missed the 8.2 boat. Now the devel tree is open again > and people are back from xmas + new year vacations, can this be picked > up for master and eventually 8.2-stable?
I can queue it, sure. Do we need to respin it to add cc: qemu-stable tags, or can it be applied as-is ? -- PMM
