All of lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Maydell <peter.maydell@linaro.org>
To: Gerd Hoffmann <kraxel@redhat.com>
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: [PULL 0/6] Firmware/edk2 20231213 patches
Date: Fri, 12 Jan 2024 16:19:09 +0000	[thread overview]
Message-ID: <CAFEAcA_-fF7fWGm_QUJa86LHJvtBk4jKvTw=OvM+EOxQzuYvWA@mail.gmail.com> (raw)
In-Reply-To: <CAFEAcA_f0Q7LkSQ2+sxgBcRQNSTenykq1R28QMuGyW22PtxW2Q@mail.gmail.com>

On Fri, 12 Jan 2024 at 12:47, Peter Maydell <peter.maydell@linaro.org> wrote:
>
> On Thu, 11 Jan 2024 at 16:28, Gerd Hoffmann <kraxel@redhat.com> wrote:
> >
> > On Thu, Jan 11, 2024 at 04:02:38PM +0000, Peter Maydell wrote:
> > > On Thu, 11 Jan 2024 at 15:52, Peter Maydell <peter.maydell@linaro.org> wrote:
> > > >
> > > > On Thu, 11 Jan 2024 at 14:01, Gerd Hoffmann <kraxel@redhat.com> wrote:
> > > > >
> > > > > 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 ?
> > >
> > > ...PS did you mean to cc qemu-stable, not the nonexistent edk2-stable
> > > on this pullreq email?
> >
> > Yes, Cc'ing qemu-stable was the intention, thanks for fixing it up.
> >
> > I'd leave it to the stable maintainer(s).  If they prefer a respin with
> > Cc qemu-stable added to all patches I surely can do that.  If being
> > notified with this reply is good enough I'm happy too.
>
> Well, it all made it through the CI fine, and I think MJT is
> fairly flexible about stable- notifications, so I'm going to
> push this merge to git.
>
>
> Applied, thanks.
>
> Please update the changelog at https://wiki.qemu.org/ChangeLog/9.0
> for any user-visible changes.

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.

thanks
-- PMM


  reply	other threads:[~2024-01-12 16:20 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 [this message]
2024-01-12 16:19             ` Peter Maydell
2024-01-15 10:20             ` Gerd Hoffmann
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='CAFEAcA_-fF7fWGm_QUJa86LHJvtBk4jKvTw=OvM+EOxQzuYvWA@mail.gmail.com' \
    --to=peter.maydell@linaro.org \
    --cc=anisinha@redhat.com \
    --cc=imammedo@redhat.com \
    --cc=kraxel@redhat.com \
    --cc=mst@redhat.com \
    --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.