From: "Ard Biesheuvel" <ardb@kernel.org>
To: Laszlo Ersek <lersek@redhat.com>
Cc: Gerd Hoffmann <kraxel@redhat.com>,
devel@edk2.groups.io, Rebecca Cran <rebecca@bsdio.com>,
Pawel Polawski <ppolawsk@redhat.com>,
Oliver Steffen <osteffen@redhat.com>,
Jordan Justen <jordan.l.justen@intel.com>,
Ard Biesheuvel <ardb+tianocore@kernel.org>,
Ray Ni <ray.ni@intel.com>, Jiewen Yao <jiewen.yao@intel.com>
Subject: Re: [PATCH v2 1/1] OvmfPkg/PlatformPei: drop S3Verification()
Date: Mon, 29 May 2023 13:41:32 +0200 [thread overview]
Message-ID: <CAMj1kXHDD+Wi5tqJh2R9-V242mhxb1Bprmaw5Bi7Hay579vFBg@mail.gmail.com> (raw)
In-Reply-To: <CAMj1kXFwhg2bwMnqoCPimyuS6V+0MbMd6-hhhWYR=NXc62gwGQ@mail.gmail.com>
On Wed, 24 May 2023 at 14:29, Ard Biesheuvel <ardb@kernel.org> wrote:
>
> On Wed, 24 May 2023 at 14:28, Laszlo Ersek <lersek@redhat.com> wrote:
> >
> > On 5/24/23 11:11, Gerd Hoffmann wrote:
> > > Not needed any more, SMM + 64-bit PEI + S3 suspend works now. While
> > > being at it also remove it from Bhyve (where it is dead code).
> > >
> > > Fixed by commits:
> > > - 8bd2028f9ac3 ("MdeModulePkg: Supporting S3 in 64bit PEI")
> > > - 6acf72901a2e ("UefiCpuPkg: Supporting S3 in 64bit PEI")
> > > See also https://bugzilla.tianocore.org/show_bug.cgi?id=4195
> > >
> > > Signed-off-by: Gerd Hoffmann <kraxel@redhat.com>
> > > Reviewed-by: Ard Biesheuvel <ardb@kernel.org>
> > > Reviewed-by: Laszlo Ersek <lersek@redhat.com>
> > > Reviewed-by: Ray Ni <ray.ni@intel.com>
> > > ---
> > > OvmfPkg/Bhyve/PlatformPei/Platform.c | 29 --------------------------
> > > OvmfPkg/PlatformPei/Platform.c | 31 ----------------------------
> > > 2 files changed, 60 deletions(-)
> >
> > I disagree with this (v2) update. Bhyve platform code and QEMU platform
> > code should not be fused into a common patch, if there's a way to avoid
> > that. The reviewers for these C files are also different. If we want to
> > modify Bhyve as a courtesy, we can certainly propose a *separate* patch
> > for that.
> >
> > If others approve this patch, I can't block it from going in; since I've
> > been CC'd (and I thought I'd comment this time), this is my view on it.
> >
>
> Thanks Laszlo. I'll split them out when applying.
Merged as #4441
prev parent reply other threads:[~2023-05-29 11:41 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-24 9:11 [PATCH v2 1/1] OvmfPkg/PlatformPei: drop S3Verification() Gerd Hoffmann
2023-05-24 12:27 ` Laszlo Ersek
2023-05-24 12:29 ` Ard Biesheuvel
2023-05-29 11:41 ` Ard Biesheuvel [this message]
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-list 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=CAMj1kXHDD+Wi5tqJh2R9-V242mhxb1Bprmaw5Bi7Hay579vFBg@mail.gmail.com \
--to=devel@edk2.groups.io \
/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