From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Mark Brown <broonie@kernel.org>
Cc: Yanteng Si <siyanteng@loongson.cn>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Next Mailing List <linux-next@vger.kernel.org>
Subject: linux-next: build warning after merge of the spi tree
Date: Mon, 11 Jan 2021 12:09:39 +1100 [thread overview]
Message-ID: <20210111120939.7d982bb2@canb.auug.org.au> (raw)
[-- Attachment #1: Type: text/plain, Size: 1320 bytes --]
Hi all,
After merging the spi tree, today's linux-next build (x86_64 allmodconfig)
produced this warning:
In file included from include/linux/kernel.h:14,
from include/linux/clk.h:13,
from drivers/spi/spi-cadence-quadspi.c:9:
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, 500U)))) {
| ^~~
Introduced by commit
8728a81b8f10 ("spi: Fix distinct pointer types warning for ARCH=mips")
--
Cheers,
Stephen Rothwell
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next reply other threads:[~2021-01-11 1:10 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-11 1:09 Stephen Rothwell [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-02-16 3:11 linux-next: build warning after merge of the spi tree Stephen Rothwell
2024-02-19 11:18 ` Dhruva Gole
2024-02-08 3:52 Stephen Rothwell
2024-02-08 11:43 ` Mark Brown
2024-02-08 13:32 ` Amadeusz Sławiński
2024-02-08 21:59 ` Stephen Rothwell
2022-06-08 4:30 Stephen Rothwell
2022-06-08 7:30 ` David Jander
2022-06-08 10:05 ` Mark Brown
2021-08-10 6:29 Stephen Rothwell
2021-08-09 5:30 Stephen Rothwell
2021-04-20 3:48 Stephen Rothwell
2021-04-20 7:56 ` Patrice CHOTARD
2021-04-06 6:48 Stephen Rothwell
2021-04-06 7:38 ` Jay Fang
2021-01-04 0:06 Stephen Rothwell
2021-01-04 7:56 ` Ardelean, Alexandru
2020-07-09 4:10 Stephen Rothwell
2020-07-09 5:29 ` Peng Fan
2020-04-28 4:16 Stephen Rothwell
2020-04-28 5:01 ` Sanjay R Mehta
2020-04-28 9:38 ` Mark Brown
2020-01-15 2:23 Stephen Rothwell
2020-01-15 9:10 ` Jean Pihet
2020-01-15 10:27 ` Stephen Rothwell
2020-01-15 11:38 ` Jean Pihet
2019-04-29 4:30 Stephen Rothwell
2019-01-29 2:02 Stephen Rothwell
2019-01-29 6:57 ` Yogesh Narayan Gaur
2019-01-29 7:25 ` Schrempf Frieder
2019-01-29 8:26 ` Stephen Rothwell
2019-01-29 8:39 ` Yogesh Narayan Gaur
2019-01-10 0:44 Stephen Rothwell
2019-01-10 0:41 Stephen Rothwell
2018-11-14 2:18 Stephen Rothwell
[not found] ` <CAP6Zq1gp+hmNkvk8D2uv8FUqTXE4+ZMPhMB7A7vLMaM6swHy4g@mail.gmail.com>
2018-11-15 19:26 ` Mark Brown
2018-08-03 4:37 Stephen Rothwell
2017-03-27 2:41 Stephen Rothwell
2017-03-27 5:33 ` Vignesh R
2010-10-14 1:59 Stephen Rothwell
2010-10-14 5:00 ` Grant Likely
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=20210111120939.7d982bb2@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=broonie@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--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).