From: Ahmad Fatoum <a.fatoum@pengutronix.de>
To: Sascha Hauer <sha@pengutronix.de>
Cc: barebox@lists.infradead.org
Subject: Re: [PATCH] include: linux/iopoll.h: silence warning when timeout_us contains *
Date: Tue, 10 Jan 2023 17:40:38 +0100 [thread overview]
Message-ID: <b07bab36-b210-0050-4b6f-02df6f12342d@pengutronix.de> (raw)
In-Reply-To: <20230110144157.GJ28911@pengutronix.de>
Hello Sascha,
On 10.01.23 15:41, Sascha Hauer wrote:
> On Mon, Jan 09, 2023 at 05:00:57PM +0100, Ahmad Fatoum wrote:
>> We evaluate timeout_us for truthiness to determine whether we are
>> entering an infinite poll loop. When timeout_us contains a
>> multiplication, GCC will warn about it and suggest replacing the *
>> with &&. Silence this warning by comparing directly against 0.
>>
>> Signed-off-by: Ahmad Fatoum <a.fatoum@pengutronix.de>
>> ---
>> include/linux/iopoll.h | 4 ++--
>> 1 file changed, 2 insertions(+), 2 deletions(-)
>>
>> diff --git a/include/linux/iopoll.h b/include/linux/iopoll.h
>> index 8bf912e173b3..b8c55583f97f 100644
>> --- a/include/linux/iopoll.h
>> +++ b/include/linux/iopoll.h
>> @@ -32,13 +32,13 @@
>> #define read_poll_timeout(op, val, cond, timeout_us, args...) \
>> ({ \
>> uint64_t start; \
>> - if (!IN_PBL && timeout_us) \
>> + if (!IN_PBL && timeout_us != 0) \
>
> You should rather put timeout_us in brackets.
Doesn't help:
drivers/mtd/nand/atmel/nand-controller.c:279:51:
warning: '*' in boolean context, suggest '&&' instead [-Wint-in-bool-context]
279 | timeout_ms * 1000);
include/linux/iopoll.h:35:25: note: in definition of macro 'read_poll_timeout'
35 | if (!IN_PBL && (timeout_us)) \
| ^~~~~~~~~~
Ok to apply?
Cheers,
Ahmad
>
> Sascha
>
>> start = get_time_ns(); \
>> for (;;) { \
>> (val) = op(args); \
>> if (cond) \
>> break; \
>> - if (!IN_PBL && timeout_us && \
>> + if (!IN_PBL && timeout_us != 0 && \
>> is_timeout(start, ((timeout_us) * USECOND))) { \
>> (val) = op(args); \
>> break; \
>> --
>> 2.30.2
>>
>>
>>
>
--
Pengutronix e.K. | |
Steuerwalder Str. 21 | http://www.pengutronix.de/ |
31137 Hildesheim, Germany | Phone: +49-5121-206917-0 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
next prev parent reply other threads:[~2023-01-10 16:42 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-09 16:00 Ahmad Fatoum
2023-01-09 18:02 ` [PATCH] fixup! " Ahmad Fatoum
2023-01-10 14:42 ` Sascha Hauer
2023-01-10 14:41 ` [PATCH] " Sascha Hauer
2023-01-10 16:40 ` Ahmad Fatoum [this message]
2023-01-11 7:39 ` Sascha Hauer
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=b07bab36-b210-0050-4b6f-02df6f12342d@pengutronix.de \
--to=a.fatoum@pengutronix.de \
--cc=barebox@lists.infradead.org \
--cc=sha@pengutronix.de \
/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