From: Michael Schierl <schierlm@gmx.de>
To: development@efficientek.com
Cc: Daniel Kiper <dkiper@net-space.pl>, grub-devel@gnu.org
Subject: Re: [PATCH v2] misc: Allow selective disabling of debug facility names
Date: Tue, 7 Dec 2021 22:01:14 +0100 [thread overview]
Message-ID: <22537d2d-ce09-2d01-400a-1f86f1debfac@gmx.de> (raw)
In-Reply-To: <20211207031742.17bd0474@crass-HP-ZBook-15-G2>
Hello Glenn,
Am 07.12.2021 um 10:17 schrieb Glenn Washburn:
>> maybe move the conditional before the assignment of ret?
>
> I'm understanding you to be suggesting to move the assignment of ret to
> after the if statement that follows it.
Correct.
> The only point I see is saving
> an assignment in the case that debug=all. Is there more to it?
No. It just bugged me to do a definitely never used assignment directly
before returning. Feel free to ignore it.
> Yep, this is an issue. It was intentional when I had the code only
> running in the case "all" was present, in which case skipping the
> condition if its the at the start of $debug is fine because the
> condition is already enabled. After changing to run also without "all"
> being present, this becomes an issue.
If "all" still was present I would probably have complained about
initializing it to +1 instead of +3 as the first three characters cannot
be a match if they are "all". :)
> I was using grub_iswordseparator in the original patch, but decided
> against it this round because the documentation states that separators
> are whitespace or comma.
Fair point. I don't think there are any common cases where this
backward-incompatible change really matters.
Regards,
Michael
next prev parent reply other threads:[~2021-12-07 21:01 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-06 17:03 [PATCH v2] misc: Allow selective disabling of debug facility names Glenn Washburn
2021-12-06 21:01 ` Michael Schierl
2021-12-07 9:17 ` Glenn Washburn
2021-12-07 21:01 ` Michael Schierl [this message]
2021-12-07 21:59 ` Glenn Washburn
2021-12-07 22:07 ` Michael Schierl
2021-12-08 0:27 ` Glenn Washburn
2021-12-09 18:41 ` Daniel Kiper
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-all 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=22537d2d-ce09-2d01-400a-1f86f1debfac@gmx.de \
--to=schierlm@gmx.de \
--cc=development@efficientek.com \
--cc=dkiper@net-space.pl \
--cc=grub-devel@gnu.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.