From: "Dionna Glaze" <dionnaglaze@google.com>
To: Robert Phelps <robert@ami.com>
Cc: devel@edk2.groups.io
Subject: Re: [edk2-devel] [PATCH 2/2] MdeModulePkg: Added call to signal New Event
Date: Wed, 9 Nov 2022 10:01:57 -0800 [thread overview]
Message-ID: <CAAH4kHY8ib2CWRhVg5GGrUjvnMOpc+2F-CA980G5jfkCFmX2Mw@mail.gmail.com> (raw)
In-Reply-To: <8217.1668015077582858880@groups.io>
>
> I can create a new patch that contains, the two Event definitions and the code that signals both events. I can use my patches that I already have and then add the code from your submission that signals the After Ready to Boot event to that.
>
> Rob
I think since Jiewen and Ard already acked my patches for
before_exit_boot_services, you might be better served by just rebasing
your after_ready_to_boot changes on my v1 series, since Michael has
said he doesn't want the after_ready_to_boot changes I had in v2.
--
-Dionna Glaze, PhD (she/her)
next prev parent reply other threads:[~2022-11-09 18:02 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-08 20:28 [edk2][PATCH 0/2] Add Events introduced in UEFI 2.9 Robert Phelps
2022-11-08 20:28 ` [PATCH 1/2] MdePkg: Add New Event Definitions from " Robert Phelps
2022-11-08 20:28 ` [PATCH 2/2] MdeModulePkg: Added call to signal New Event Robert Phelps
2022-11-08 23:42 ` [edk2-devel] " Dionna Glaze
2022-11-09 15:49 ` Robert Phelps
2022-11-09 16:21 ` Dionna Glaze
2022-11-09 16:52 ` Michael D Kinney
2022-11-09 16:58 ` Dionna Glaze
2022-11-09 17:31 ` Robert Phelps
2022-11-09 18:01 ` Dionna Glaze [this message]
2022-11-08 22:44 ` [edk2][PATCH 0/2] Add Events introduced in UEFI 2.9 Michael D Kinney
2022-11-09 16:10 ` [edk2-devel] " Robert Phelps
2022-12-07 1:08 ` 回复: " gaoliming
2022-12-14 17:49 ` Robert Phelps
2022-12-21 1:16 ` 回复: [edk2-devel] " gaoliming
2023-01-11 19:11 ` [edk2-devel] " Robert Phelps
2023-01-11 21:16 ` Michael D Kinney
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=CAAH4kHY8ib2CWRhVg5GGrUjvnMOpc+2F-CA980G5jfkCFmX2Mw@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