From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Srinivas Kandagatla <srinivas.kandagatla@linaro.org>
Cc: Linux Next Mailing List <linux-next@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
PrasannaKumar Muralidharan <prasannatsmkumar@gmail.com>,
Mathieu Malaterre <malat@debian.org>,
"H. Nikolaus Schaller" <hns@goldelico.com>,
Paul Cercueil <paul@crapouillou.net>
Subject: linux-next: build warning after merge of the nvmem tree
Date: Fri, 6 Mar 2020 15:28:27 +1100 [thread overview]
Message-ID: <20200306152827.6fe507bd@canb.auug.org.au> (raw)
[-- Attachment #1: Type: text/plain, Size: 1253 bytes --]
Hi all,
After merging the nvmem tree, today's linux-next build (x86_64
allmodconfig) produced this warning:
In file included from include/linux/clk.h:13,
from drivers/nvmem/jz4780-efuse.c:25:
drivers/nvmem/jz4780-efuse.c: In function 'jz4780_efuse_read':
include/linux/kernel.h:842:29: warning: comparison of distinct pointer types lacks a cast
842 | (!!(sizeof((typeof(x) *)1 == (typeof(y) *)1)))
| ^~
include/linux/kernel.h:856:4: note: in expansion of macro '__typecheck'
856 | (__typecheck(x, y) && __no_side_effects(x, y))
| ^~~~~~~~~~~
include/linux/kernel.h:866:24: note: in expansion of macro '__safe_cmp'
866 | __builtin_choose_expr(__safe_cmp(x, y), \
| ^~~~~~~~~~
include/linux/kernel.h:875:19: note: in expansion of macro '__careful_cmp'
875 | #define min(x, y) __careful_cmp(x, y, <)
| ^~~~~~~~~~~~~
drivers/nvmem/jz4780-efuse.c:76:24: note: in expansion of macro 'min'
76 | unsigned int chunk = min(bytes, (start + JZ_EFU_READ_SIZE)
| ^~~
Introduced by commit
50a09dfd394a ("nvmem: add driver for JZ4780 efuse")
--
Cheers,
Stephen Rothwell
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next reply other threads:[~2020-03-06 4:28 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-06 4:28 Stephen Rothwell [this message]
2020-03-06 10:03 ` H. Nikolaus Schaller
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=20200306152827.6fe507bd@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=hns@goldelico.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=malat@debian.org \
--cc=paul@crapouillou.net \
--cc=prasannatsmkumar@gmail.com \
--cc=srinivas.kandagatla@linaro.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
all inboxes | Powered by JetHome®