From: "Michael Brown" <mcb30@ipxe.org>
To: devel@edk2.groups.io, lersek@redhat.com
Cc: Gerd Hoffmann <kraxel@redhat.com>
Subject: Re: [edk2-devel] [PATCH 2/2] OvmfPkg: Relax assertion that interrupts do not occur at TPL_HIGH_LEVEL
Date: Tue, 9 May 2023 12:04:18 +0000 [thread overview]
Message-ID: <010201880065e903-bb283d95-dc61-427c-8ad7-b00f75c064a1-000000@eu-west-1.amazonses.com> (raw)
In-Reply-To: <d7c6dee6-fb05-559b-e4ba-a3f5af0951ea@redhat.com>
On 09/05/2023 09:35, Laszlo Ersek wrote:
> Thank you for the patch; I do apologize about splitting hairs. The
> debugging was difficult, and you *are* working around a bug here -- but
> I'd really like our tone of voice to be positive here, simply because of
> the stunningly positive attitude I've experienced from Microsoft.
No problem. Patch v2 to follow.
Michael
prev parent reply other threads:[~2023-05-09 12:04 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-03 7:19 [PATCH v2 1/1] OvmfPkg/NestedInterruptTplLib: replace ASSERT() with a warning logged Gerd Hoffmann
2023-05-05 14:10 ` [edk2-devel] " Michael Brown
2023-05-05 18:56 ` Laszlo Ersek
2023-05-05 23:27 ` Michael Brown
2023-05-05 23:57 ` Ard Biesheuvel
2023-05-08 6:45 ` Laszlo Ersek
2023-05-09 9:13 ` Ard Biesheuvel
2023-05-08 6:38 ` Laszlo Ersek
2023-05-08 21:31 ` [PATCH 0/2] OvmfPkg: Relax assertion that interrupts do not occur at TPL_HIGH_LEVEL Michael Brown
2023-05-09 7:05 ` Gerd Hoffmann
2023-05-09 8:43 ` Laszlo Ersek
2023-05-09 12:08 ` [edk2-devel] " Michael Brown
2023-05-09 13:27 ` Laszlo Ersek
[not found] ` <20230508213100.3949708-1-mcb30@ipxe.org>
2023-05-08 21:31 ` [PATCH 1/2] OvmfPkg: Clarify invariants for NestedInterruptTplLib Michael Brown
2023-05-08 21:31 ` [PATCH 2/2] OvmfPkg: Relax assertion that interrupts do not occur at TPL_HIGH_LEVEL Michael Brown
2023-05-09 8:35 ` Laszlo Ersek
2023-05-09 9:42 ` Gerd Hoffmann
2023-05-09 12:04 ` Michael Brown [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=010201880065e903-bb283d95-dc61-427c-8ad7-b00f75c064a1-000000@eu-west-1.amazonses.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