From: Gerd Hoffmann <kraxel@redhat.com>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: qemu-devel@nongnu.org, "Igor Mammedov" <imammedo@redhat.com>,
"Ani Sinha" <anisinha@redhat.com>,
"Philippe Mathieu-Daudé" <philmd@linaro.org>,
"Michael S. Tsirkin" <mst@redhat.com>,
qemu-stable <qemu-stable@nongnu.org>
Subject: Re: Re: Re: [PULL 0/6] Firmware/edk2 20231213 patches
Date: Mon, 15 Jan 2024 11:20:29 +0100 [thread overview]
Message-ID: <7u5v67zlt5aapyinxbc4dgdiivtx4cr5mttdck6jzfknfb2ni2@lscetlkzwvjy> (raw)
In-Reply-To: <CAFEAcA_-fF7fWGm_QUJa86LHJvtBk4jKvTw=OvM+EOxQzuYvWA@mail.gmail.com>
Hi,
> PS: when are we likely to be able to update to a proper released
> EDK2 ? Running with a git snapshot isn't ideal, so if we can
> move to an EDK2 release version within this QEMU cycle that would
> be nice.
Next release should be tagged by end of February, so if the qemu 9.0
schedule is simliar to the 8.0 schedule this is before soft freeze
and an update should be no problem.
take care,
Gerd
next prev parent reply other threads:[~2024-01-15 10:21 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-13 10:50 [PULL 0/6] Firmware/edk2 20231213 patches Gerd Hoffmann
2023-12-13 10:50 ` [PULL 1/6] tests/acpi: allow tests/data/acpi/virt/SSDT.memhp changes Gerd Hoffmann
2023-12-13 10:50 ` [PULL 2/6] edk2: update to git snapshot Gerd Hoffmann
2023-12-13 10:50 ` [PULL 3/6] edk2: update build config, set PcdUninstallMemAttrProtocol = TRUE Gerd Hoffmann
2023-12-13 10:50 ` [PULL 5/6] tests/acpi: update expected data files Gerd Hoffmann
2023-12-13 10:50 ` [PULL 6/6] tests/acpi: disallow tests/data/acpi/virt/SSDT.memhp changes Gerd Hoffmann
2023-12-13 10:54 ` Ani Sinha
2023-12-13 14:33 ` Michael S. Tsirkin
2023-12-13 14:39 ` Ani Sinha
2023-12-13 15:03 ` Michael S. Tsirkin
2023-12-13 15:14 ` Gerd Hoffmann
2023-12-13 15:17 ` Michael S. Tsirkin
2023-12-13 15:22 ` Ani Sinha
2024-01-11 14:01 ` [PULL 0/6] Firmware/edk2 20231213 patches Gerd Hoffmann
2024-01-11 15:52 ` Peter Maydell
2024-01-11 16:02 ` Peter Maydell
2024-01-11 16:28 ` Gerd Hoffmann
2024-01-12 12:47 ` Peter Maydell
2024-01-12 16:19 ` Peter Maydell
2024-01-12 16:19 ` Peter Maydell
2024-01-15 10:20 ` Gerd Hoffmann [this message]
2024-01-17 10:16 ` Michael Tokarev
2024-01-17 14:29 ` Gerd Hoffmann
2024-01-18 12:56 ` Peter Maydell
2024-01-12 14:27 ` Michael Tokarev
2024-01-12 14:30 ` Michael Tokarev
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=7u5v67zlt5aapyinxbc4dgdiivtx4cr5mttdck6jzfknfb2ni2@lscetlkzwvjy \
--to=kraxel@redhat.com \
--cc=anisinha@redhat.com \
--cc=imammedo@redhat.com \
--cc=mst@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=philmd@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=qemu-stable@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.