mail archive of the barebox mailing list
 help / color / mirror / Atom feed
From: Sascha Hauer <sha@pengutronix.de>
To: Ahmad Fatoum <a.fatoum@pengutronix.de>
Cc: barebox@lists.infradead.org
Subject: Re: [PATCH] include: linux/iopoll.h: silence warning when timeout_us contains *
Date: Wed, 11 Jan 2023 08:39:22 +0100	[thread overview]
Message-ID: <20230111073922.GB24755@pengutronix.de> (raw)
In-Reply-To: <b07bab36-b210-0050-4b6f-02df6f12342d@pengutronix.de>

On Tue, Jan 10, 2023 at 05:40:38PM +0100, Ahmad Fatoum wrote:
> 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?

Yes, ok. Could you resend? git b4 seems to get confused by this series.
It tries to apply the fixup first.

Sascha

-- 
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 |



      reply	other threads:[~2023-01-11  7:40 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
2023-01-11  7:39     ` Sascha Hauer [this message]

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=20230111073922.GB24755@pengutronix.de \
    --to=sha@pengutronix.de \
    --cc=a.fatoum@pengutronix.de \
    --cc=barebox@lists.infradead.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox