From: "Dionna Glaze" <dionnaglaze@google.com>
To: "Kinney, Michael D" <michael.d.kinney@intel.com>
Cc: "devel@edk2.groups.io" <devel@edk2.groups.io>,
Gerd Hoffmann <kraxel@redhat.com>,
James Bottomley <jejb@linux.ibm.com>,
"Yao, Jiewen" <jiewen.yao@intel.com>,
Tom Lendacky <thomas.lendacky@amd.com>,
Ard Biesheuvel <ardb@kernel.org>,
"Xu, Min M" <min.m.xu@intel.com>, Andrew Fish <afish@apple.com>,
"Ni, Ray" <ray.ni@intel.com>
Subject: Re: [edk2-devel] [PATCH 3/3] MdeModulePkg: Notify BeforeExitBootServices in CoreExitBootServices
Date: Thu, 10 Nov 2022 08:43:55 -0800 [thread overview]
Message-ID: <CAAH4kHZHuT=DWr_oGxNKij_opTMCHNBYBXCdKTtWpydapzT+fw@mail.gmail.com> (raw)
In-Reply-To: <CO1PR11MB49291815FC41C87C087D8154D23E9@CO1PR11MB4929.namprd11.prod.outlook.com>
> Reviewed-by: Michael D Kinney <michael.d.kinney@intel.com>
Great, thanks Michael. With all three patches reviewed/acked, does
that mean they get merged, or what else has to be done? I'm new to
this.
--
-Dionna Glaze, PhD (she/her)
next prev parent reply other threads:[~2022-11-10 16:44 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-08 16:46 [PATCH 0/3] SEV-SNP accepted memory and BeforeExitBootServices Dionna Glaze
2022-11-08 16:46 ` [PATCH 1/3] OvmfPkg: Realize EfiMemoryAcceptProtocol in AmdSevDxe Dionna Glaze
2022-11-08 16:51 ` Yao, Jiewen
2022-11-08 16:46 ` [PATCH 2/3] MdePkg: Add EFI_EVENT_BEFORE_EXIT_BOOT_SERVICES_GUID Dionna Glaze
2022-11-08 18:11 ` [edk2-devel] " Michael D Kinney
2022-11-09 18:56 ` Michael D Kinney
2022-11-08 16:46 ` [PATCH 3/3] MdeModulePkg: Notify BeforeExitBootServices in CoreExitBootServices Dionna Glaze
2022-11-09 18:56 ` [edk2-devel] " Michael D Kinney
2022-11-10 16:43 ` Dionna Glaze [this message]
2022-11-10 16:55 ` Michael D Kinney
2023-01-11 23:08 ` Dionna Glaze
2023-01-12 12:24 ` Laszlo Ersek
2023-01-12 13:38 ` Ard Biesheuvel
2023-01-12 15:32 ` Laszlo Ersek
2023-01-12 16:09 ` Dionna Glaze
2023-01-12 17:03 ` Laszlo Ersek
2023-01-13 9:03 ` Ard Biesheuvel
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='CAAH4kHZHuT=DWr_oGxNKij_opTMCHNBYBXCdKTtWpydapzT+fw@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