From: kbuild test robot <lkp@intel.com>
To: Vladimir Oltean <vladimir.oltean@nxp.com>
Cc: kbuild-all@lists.01.org, linux-kernel@vger.kernel.org,
Mark Brown <broonie@kernel.org>
Subject: drivers/spi/spi-fsl-dspi.c:261:17: sparse: sparse: incorrect type in assignment (different base types)
Date: Thu, 28 May 2020 04:16:47 +0800 [thread overview]
Message-ID: <202005280442.X0rhkVyY%lkp@intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 2410 bytes --]
tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
head: b0c3ba31be3e45a130e13b278cf3b90f69bda6f6
commit: 6c1c26ecd9a31c24f9ea7dfb174528141dd32361 spi: spi-fsl-dspi: Accelerate transfers using larger word size if possible
date: 3 months ago
config: arm64-randconfig-s031-20200527 (attached as .config)
compiler: aarch64-linux-gcc (GCC) 9.3.0
reproduce:
# apt-get install sparse
# sparse version: v0.6.1-240-gf0fe1cd9-dirty
git checkout 6c1c26ecd9a31c24f9ea7dfb174528141dd32361
# save the attached .config to linux build tree
make W=1 C=1 ARCH=arm64 CF='-fdiagnostic-prefix -D__CHECK_ENDIAN__'
If you fix the issue, kindly add following tag as appropriate
Reported-by: kbuild test robot <lkp@intel.com>
sparse warnings: (new ones prefixed by >>)
>> drivers/spi/spi-fsl-dspi.c:261:17: sparse: sparse: incorrect type in assignment (different base types) @@ expected unsigned int [usertype] @@ got restricted __be32 [usertype] @@
drivers/spi/spi-fsl-dspi.c:261:17: sparse: expected unsigned int [usertype]
drivers/spi/spi-fsl-dspi.c:261:17: sparse: got restricted __be32 [usertype]
drivers/spi/spi-fsl-dspi.c:267:28: sparse: sparse: cast to restricted __be32
>> drivers/spi/spi-fsl-dspi.c:273:17: sparse: sparse: incorrect type in assignment (different base types) @@ expected unsigned int [usertype] @@ got restricted __be16 [usertype] @@
drivers/spi/spi-fsl-dspi.c:273:17: sparse: expected unsigned int [usertype]
drivers/spi/spi-fsl-dspi.c:273:17: sparse: got restricted __be16 [usertype]
drivers/spi/spi-fsl-dspi.c:279:28: sparse: sparse: cast to restricted __be16
vim +261 drivers/spi/spi-fsl-dspi.c
258
259 static void dspi_8on32_host_to_dev(struct fsl_dspi *dspi, u32 *txdata)
260 {
> 261 *txdata = cpu_to_be32(*(u32 *)dspi->tx);
262 dspi->tx += sizeof(u32);
263 }
264
265 static void dspi_8on32_dev_to_host(struct fsl_dspi *dspi, u32 rxdata)
266 {
267 *(u32 *)dspi->rx = be32_to_cpu(rxdata);
268 dspi->rx += sizeof(u32);
269 }
270
271 static void dspi_8on16_host_to_dev(struct fsl_dspi *dspi, u32 *txdata)
272 {
> 273 *txdata = cpu_to_be16(*(u16 *)dspi->tx);
274 dspi->tx += sizeof(u16);
275 }
276
---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all@lists.01.org
[-- Attachment #2: .config.gz --]
[-- Type: application/gzip, Size: 42984 bytes --]
reply other threads:[~2020-05-27 20:53 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=202005280442.X0rhkVyY%lkp@intel.com \
--to=lkp@intel.com \
--cc=broonie@kernel.org \
--cc=kbuild-all@lists.01.org \
--cc=linux-kernel@vger.kernel.org \
--cc=vladimir.oltean@nxp.com \
/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®