From: James Bottomley <James.Bottomley@HansenPartnership.com>
To: Xu Wang <vulab@iscas.ac.cn>,
dhowells@redhat.com, dwmw2@infradead.org,
keyrings@vger.kernel.org
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] scrpits: Remove unneeded assignment parentheses
Date: Thu, 21 May 2020 07:14:02 -0700 [thread overview]
Message-ID: <1590070442.4669.12.camel@HansenPartnership.com> (raw)
In-Reply-To: <20200521063226.7434-1-vulab@iscas.ac.cn>
On Thu, 2020-05-21 at 06:32 +0000, Xu Wang wrote:
> Remove unneeded assignment parentheses.
I really don't think this is a good idea. Best practice for macros is
to parenthesize every argument even if there are technically some cases
where it's unnecessary because the problems in the majority cases are
huge and unexpected.
James
> Signed-off-by: Xu Wang <vulab@iscas.ac.cn>
> ---
> scripts/extract-cert.c | 2 +-
> scripts/sign-file.c | 2 +-
> 2 files changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/scripts/extract-cert.c b/scripts/extract-cert.c
> index b071bf476fea..8005911926b8 100644
> --- a/scripts/extract-cert.c
> +++ b/scripts/extract-cert.c
> @@ -61,7 +61,7 @@ static void drain_openssl_errors(void)
>
> #define ERR(cond, fmt, ...) \
> do { \
> - bool __cond = (cond); \
> + bool __cond = cond; \
> display_openssl_errors(__LINE__); \
> if (__cond) { \
> err(1, fmt, ## __VA_ARGS__); \
> diff --git a/scripts/sign-file.c b/scripts/sign-file.c
> index fbd34b8e8f57..9ea08b07a0aa 100644
> --- a/scripts/sign-file.c
> +++ b/scripts/sign-file.c
> @@ -104,7 +104,7 @@ static void drain_openssl_errors(void)
>
> #define ERR(cond, fmt, ...) \
> do { \
> - bool __cond = (cond); \
> + bool __cond = cond; \
> display_openssl_errors(__LINE__); \
> if (__cond) { \
> err(1, fmt, ## __VA_ARGS__); \
next prev parent reply other threads:[~2020-05-21 14:14 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-21 6:32 [PATCH] scrpits: Remove unneeded assignment parentheses Xu Wang
2020-05-21 14:14 ` James Bottomley [this message]
2020-05-21 14:28 ` David Howells
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=1590070442.4669.12.camel@HansenPartnership.com \
--to=james.bottomley@hansenpartnership.com \
--cc=dhowells@redhat.com \
--cc=dwmw2@infradead.org \
--cc=keyrings@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=vulab@iscas.ac.cn \
/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