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 08:21:47 -0800 [thread overview]
Message-ID: <CAAH4kHZ_8G0RmVkxrtJeMrEuuM5WHHq=C2Z+uKhhi+d7ikm=MA@mail.gmail.com> (raw)
In-Reply-To: <15148.1668008980112037683@groups.io>
> So how should we want to handle this. Leave yours in or leave mine in.
Given that I'm not particularly confident in how I've implemented the
after_ready_to_boot spec, and you haven't implemented it, I'm not
sure. I'm pursuing the before_exit_boot_services implementation to
solve a problem in confidential compute as part of my job, so I think
I have the motivation to keep pushing on this. Let's go with mine
since it's further along. I'd appreciate a Reviewed-by if you agree
with the implementations.
--
-Dionna Glaze, PhD (she/her)
next prev parent reply other threads:[~2022-11-09 16:21 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 [this message]
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
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='CAAH4kHZ_8G0RmVkxrtJeMrEuuM5WHHq=C2Z+uKhhi+d7ikm=MA@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