From: "Laszlo Ersek" <lersek@redhat.com>
To: devel@edk2.groups.io, michael.d.kinney@intel.com
Cc: Jiewen Yao <jiewen.yao@intel.com>,
Jian J Wang <jian.j.wang@intel.com>,
Chao Zhang <chao.b.zhang@intel.com>
Subject: Re: [edk2-devel] [Patch v2 1/2] SecurityPkg: Replace EFI_D_* with DEBUG_*
Date: Tue, 22 Oct 2019 20:05:42 +0200 [thread overview]
Message-ID: <b51d2bd8-7b38-c460-a5f0-625f7e2134e6@redhat.com> (raw)
In-Reply-To: <20191022173716.27700-2-michael.d.kinney@intel.com>
Hi Mike,
On 10/22/19 19:37, Michael D Kinney wrote:
> Update all DEBUG() macros in the SecurityPkg to use
> DEBUG_ instead of EFI_D_. This is required to pass
> PatchCheck.py checks.
[...]
> 45 files changed, 410 insertions(+), 410 deletions(-)
(
If the SecurityPkg maintainers are happy with this patch, then it's not
my place to complain.
I'd just like to point out that I'd object to such a patch for OvmfPkg.
Such sweeping conversions are difficult to review (they are also
difficult to implement -- I think mass search&replace is not too safe
without human review).
New code should not add EFI_D_* usage, of course.
I'd expect PatchCheck.py to complain about EFI_D_* only on lines that
are added by a patch, not on lines being removed, or present in the
context. Is that not the case?
... Hm, looking at patch#2, it seems that some spelling errors affect
debug messages. Therefore, some of the typo fixes do turn EFI_D_* macros
into new lines. Given that there is a huge number of typo fixes (205
lines, apparently), I guess it makes sense to separate out the EFI_D_*
conversion. It's up to the package owners whether they prefer reviewing
- 410 lines of EFI_D_* massaging, plus 205 lines of typo fixes,
- or 205 lines of { EFI_D_* conversion, plus typo fix }.
For OvmfPkg, my choice would likely be (assuming such a large diffstat):
- fix EFI_D_*, one patch per module, and only on lines affected by typos,
- fix typos, one patch per module.
I could suspend and resume a review like that more easily.
)
Thanks
Laszlo
next prev parent reply other threads:[~2019-10-22 18:05 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-22 17:37 [Patch v2 0/2] SecurityPkg: Fix spelling errors Michael D Kinney
2019-10-22 17:37 ` [Patch v2 1/2] SecurityPkg: Replace EFI_D_* with DEBUG_* Michael D Kinney
2019-10-22 18:05 ` Laszlo Ersek [this message]
2019-10-22 18:27 ` [edk2-devel] " Michael D Kinney
2019-10-22 23:16 ` Laszlo Ersek
2019-10-23 6:21 ` Wang, Jian J
2019-10-22 17:37 ` [Patch v2 2/2] SecurityPkg: Fix spelling errors 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=b51d2bd8-7b38-c460-a5f0-625f7e2134e6@redhat.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