From: Geert Uytterhoeven <geert@linux-m68k.org>
To: Nathan Chancellor <natechancellor@gmail.com>
Cc: Yanteng Si <siyanteng@loongson.cn>,
Mark Brown <broonie@kernel.org>,
Philipp Zabel <p.zabel@pengutronix.de>,
linux-spi <linux-spi@vger.kernel.org>,
Huacai Chen <chenhuacai@gmail.com>,
Jiaxun Yang <jiaxun.yang@flygoat.com>,
Yanteng Si <siyanteng@gmail.com>
Subject: Re: [PATCH] SPI: Fix distinct pointer types warning for ARCH=MIPS
Date: Mon, 11 Jan 2021 09:14:59 +0100 [thread overview]
Message-ID: <CAMuHMdUKnwGDf3siiF3WsWw4_tt0Q3_YSfLpjriA56w68my7DQ@mail.gmail.com> (raw)
In-Reply-To: <20210107173004.GA2169893@ubuntu-m3-large-x86>
Hi Nathan,
On Thu, Jan 7, 2021 at 6:31 PM Nathan Chancellor
<natechancellor@gmail.com> wrote:
> On Thu, Jan 07, 2021 at 07:57:04PM +0800, Yanteng Si wrote:
> > Fix a new warning report by build for make ARCH=MIPS allmodconfig:
> >
> > drivers/spi/spi-cadence-quadspi.c: In function 'cqspi_direct_read_execute':
> > ./include/linux/minmax.h:18:28: warning: comparison of distinct pointer types lacks a cast
> > 18 | (!!(sizeof((typeof(x) *)1 == (typeof(y) *)1)))
> > | ^~
> > ./include/linux/minmax.h:32:4: note: in expansion of macro '__typecheck'
> > 32 | (__typecheck(x, y) && __no_side_effects(x, y))
> > | ^~~~~~~~~~~
> > ./include/linux/minmax.h:42:24: note: in expansion of macro '__safe_cmp'
> > 42 | __builtin_choose_expr(__safe_cmp(x, y), \
> > | ^~~~~~~~~~
> > ./include/linux/minmax.h:58:19: note: in expansion of macro '__careful_cmp'
> > 58 | #define max(x, y) __careful_cmp(x, y, >)
> > | ^~~~~~~~~~~~~
> > drivers/spi/spi-cadence-quadspi.c:1153:24: note: in expansion of macro 'max'
> > 1153 | msecs_to_jiffies(max(len, 500UL)))) {
> > | ^~~
> >
> > "len" is unsigned,however,"500" is unsigned long.
len is size_t, which us either unsigned int or unsigned long.
> > Signed-off-by: Yanteng Si <siyanteng@loongson.cn>
> > ---
> > drivers/spi/spi-cadence-quadspi.c | 2 +-
> > 1 file changed, 1 insertion(+), 1 deletion(-)
> >
> > diff --git a/drivers/spi/spi-cadence-quadspi.c b/drivers/spi/spi-cadence-quadspi.c
> > index 06a65e9a8a60..576610ba1118 100644
> > --- a/drivers/spi/spi-cadence-quadspi.c
> > +++ b/drivers/spi/spi-cadence-quadspi.c
> > @@ -1150,7 +1150,7 @@ static int cqspi_direct_read_execute(struct cqspi_flash_pdata *f_pdata,
> >
> > dma_async_issue_pending(cqspi->rx_chan);
> > if (!wait_for_completion_timeout(&cqspi->rx_dma_complete,
> > - msecs_to_jiffies(max(len, 500UL)))) {
> > + msecs_to_jiffies(max(len, 500U)))) {
> > dmaengine_terminate_sync(cqspi->rx_chan);
> > dev_err(dev, "DMA wait_for_completion_timeout\n");
> > ret = -ETIMEDOUT;
> > --
> > 2.27.0
> >
>
> Isn't this just going to cause warnings on 64-bit platforms now because
> size_t is defined as unsigned long and it will now be compared against
> unsigned int? This fix should work for everyone, not sure how pretty it
Yes it is!
> is though.
> --- a/drivers/spi/spi-cadence-quadspi.c
> +++ b/drivers/spi/spi-cadence-quadspi.c
> @@ -1150,7 +1150,7 @@ static int cqspi_direct_read_execute(struct cqspi_flash_pdata *f_pdata,
>
> dma_async_issue_pending(cqspi->rx_chan);
> if (!wait_for_completion_timeout(&cqspi->rx_dma_complete,
> - msecs_to_jiffies(max(len, 500UL)))) {
> + msecs_to_jiffies(max_t(size_t, len, 500)))) {
> dmaengine_terminate_sync(cqspi->rx_chan);
> dev_err(dev, "DMA wait_for_completion_timeout\n");
> ret = -ETIMEDOUT;
Reviewed-by: Geert Uytterhoeven <geert+renesas@glider.be>
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org
In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
-- Linus Torvalds
next prev parent reply other threads:[~2021-01-11 8:15 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-07 11:57 [PATCH] SPI: Fix distinct pointer types warning for ARCH=MIPS Yanteng Si
2021-01-07 13:53 ` Mark Brown
2021-01-07 17:30 ` Nathan Chancellor
2021-01-11 8:14 ` Geert Uytterhoeven [this message]
2021-01-08 16:30 ` Mark Brown
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=CAMuHMdUKnwGDf3siiF3WsWw4_tt0Q3_YSfLpjriA56w68my7DQ@mail.gmail.com \
--to=geert@linux-m68k.org \
--cc=broonie@kernel.org \
--cc=chenhuacai@gmail.com \
--cc=jiaxun.yang@flygoat.com \
--cc=linux-spi@vger.kernel.org \
--cc=natechancellor@gmail.com \
--cc=p.zabel@pengutronix.de \
--cc=siyanteng@gmail.com \
--cc=siyanteng@loongson.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;
as well as URLs for NNTP newsgroup(s).