public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
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: Wed, 11 Jan 2023 15:08:01 -0800	[thread overview]
Message-ID: <CAAH4kHaK=utUoFfJFHPjV4k1r2Wq1UwKXhKZ7q0Tzqu_VHwziA@mail.gmail.com> (raw)
In-Reply-To: <CO1PR11MB492971F2F94677E153F625ADD2019@CO1PR11MB4929.namprd11.prod.outlook.com>

On Thu, Nov 10, 2022 at 8:55 AM Kinney, Michael D
<michael.d.kinney@intel.com> wrote:
>
> Hi Dionna,
>
> https://github.com/tianocore/tianocore.github.io/wiki/EDK-II-Development-Process
>
> I think you are at step 13.  If you have not done so already, please update the
> commit messages with all the Reviewed-by and Acked-by tags and make sure your
> branch is rebased against the latest edk2/master and update the PR with that
> content and verify that all EDK II CI checks pass.
>
> At that point, it is the responsibility of the EDK II Maintainers to review
> the final state of the PR and set the "push" label if everything looks correct.
>
> At this moment, we are in Soft Freeze and will be in Hard Freeze for the next
> 2 weeks.  If this is considered critical for the stable tag release, then
> please send a request to Liming with justification for stable tag.  Otherwise,
> it will be merged after the stable tag release.
>
> https://github.com/tianocore/tianocore.github.io/wiki/EDK-II-Release-Planning
>
> Thanks,
>
> Mike
>

Hi Mike, my PR was closed without comment
https://github.com/tianocore/edk2/pull/3623 so I rebased and created a
new PR after the holidays and hard freeze. I hope this isn't
considered bad practice https://github.com/tianocore/edk2/pull/3885

-- 
-Dionna Glaze, PhD (she/her)

  reply	other threads:[~2023-01-11 23:08 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
2022-11-10 16:55       ` Michael D Kinney
2023-01-11 23:08         ` Dionna Glaze [this message]
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='CAAH4kHaK=utUoFfJFHPjV4k1r2Wq1UwKXhKZ7q0Tzqu_VHwziA@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