From: "Michael Brown" <mcb30@ipxe.org>
To: devel@edk2.groups.io, lersek@redhat.com
Cc: Gerd Hoffmann <kraxel@redhat.com>,
Oliver Steffen <osteffen@redhat.com>,
Pawel Polawski <ppolawsk@redhat.com>,
Jiewen Yao <jiewen.yao@intel.com>,
Ard Biesheuvel <ardb+tianocore@kernel.org>,
Jordan Justen <jordan.l.justen@intel.com>
Subject: Re: [edk2-devel] [PATCH 0/2] OvmfPkg: Relax assertion that interrupts do not occur at TPL_HIGH_LEVEL
Date: Tue, 9 May 2023 12:08:26 +0000 [thread overview]
Message-ID: <010201880069b0b6-6a5f2d29-9bab-44b2-aa25-0a7507daf587-000000@eu-west-1.amazonses.com> (raw)
In-Reply-To: <50bf1804-70ba-dfff-73ad-d2afdbedf5e7@redhat.com>
On 09/05/2023 09:43, Laszlo Ersek wrote:
> I'm not subscribed to the list, so I don't have a copy of patch#1. I've
> checked patch#1 at this URL:
>
> https://listman.redhat.com/archives/edk2-devel-archive/2023-May/063591.html
>
> and I'll comment on it using the cover letter:
>
> I really like that patch, with one stylistic exception: in edk2,
> explicit FALSE and TRUE comparisons are not desired. So I suggest:
>
> ASSERT (!GetInterruptState ());
>
> Twice.
>
> In fact, I *think* that if you run uncrustify with the edk2 config on
> the patch, then it will rewrite that code.
I built and ran uncrustify with the edk2 config but it did not modify
the code. (I did check that it would fix other deliberate errors such
as extra whitespace, so I don't think this was an error in my setup.)
I will send through v2 with the explicit "== FALSE" still present, for
consistency with the rest of the code in that file. (I think I vaguely
remember someone asking me to add the explicit comparisons when I first
submitted the code.) I'm happy for there to be a follow up patch to
change the coding style to remove all of the explicit boolean
comparisons, if that is what is wanted.
Thanks,
Michael
next prev parent reply other threads:[~2023-05-09 12:08 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 ` Michael Brown [this message]
2023-05-09 13:27 ` [edk2-devel] " 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 ` [edk2-devel] " Michael Brown
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=010201880069b0b6-6a5f2d29-9bab-44b2-aa25-0a7507daf587-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