From: kernel test robot <lkp@intel.com>
To: Khalil Blaiech <kblaiech@mellanox.com>
Cc: kbuild-all@lists.01.org,
Linux Memory Management List <linux-mm@kvack.org>,
Wolfram Sang <wsa-dev@sang-engineering.com>,
Vadim Pasternak <vadimp@mellanox.com>
Subject: [linux-next:master 10691/14813] drivers/i2c/busses/i2c-mlxbf.c:513:21: sparse: sparse: cast to restricted __be32
Date: Mon, 12 Oct 2020 21:10:19 +0800 [thread overview]
Message-ID: <202010122115.lA9XwEMl-lkp@intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 3347 bytes --]
tree: https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master
head: 148fdf990dee4efd23c1114811b205de9c966680
commit: b5b5b32081cd206baa6e58cca7f112d9723785d6 [10691/14813] i2c: mlxbf: I2C SMBus driver for Mellanox BlueField SoC
config: arm64-randconfig-s031-20201012 (attached as .config)
compiler: aarch64-linux-gcc (GCC) 9.3.0
reproduce:
wget https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross
chmod +x ~/bin/make.cross
# apt-get install sparse
# sparse version: v0.6.3-rc1-dirty
# https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/?id=b5b5b32081cd206baa6e58cca7f112d9723785d6
git remote add linux-next https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git
git fetch --no-tags linux-next master
git checkout b5b5b32081cd206baa6e58cca7f112d9723785d6
# save the attached .config to linux build tree
COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-9.3.0 make.cross C=1 CF='-fdiagnostic-prefix -D__CHECK_ENDIAN__' ARCH=arm64
If you fix the issue, kindly add following tag as appropriate
Reported-by: kernel test robot <lkp@intel.com>
"sparse warnings: (new ones prefixed by >>)"
>> drivers/i2c/busses/i2c-mlxbf.c:513:21: sparse: sparse: cast to restricted __be32
>> drivers/i2c/busses/i2c-mlxbf.c:513:21: sparse: sparse: cast to restricted __be32
>> drivers/i2c/busses/i2c-mlxbf.c:513:21: sparse: sparse: cast to restricted __be32
>> drivers/i2c/busses/i2c-mlxbf.c:513:21: sparse: sparse: cast to restricted __be32
>> drivers/i2c/busses/i2c-mlxbf.c:513:21: sparse: sparse: cast to restricted __be32
>> drivers/i2c/busses/i2c-mlxbf.c:513:21: sparse: sparse: cast to restricted __be32
>> drivers/i2c/busses/i2c-mlxbf.c:527:35: sparse: sparse: cast from restricted __be32
vim +513 drivers/i2c/busses/i2c-mlxbf.c
501
502 /*
503 * This function is used to read data from Master GW Data Descriptor.
504 * Data bytes in the Master GW Data Descriptor are shifted left so the
505 * data starts at the MSB of the descriptor registers as set by the
506 * underlying hardware. TYU_READ_DATA enables byte swapping while
507 * reading data bytes, and MUST be called by the SMBus read routines
508 * to copy data from the 32 * 32-bit HW Data registers a.k.a Master GW
509 * Data Descriptor.
510 */
511 static u32 mlxbf_i2c_read_data(void __iomem *io, int reg)
512 {
> 513 return (u32)be32_to_cpu(mlxbf_i2c_read(io, reg));
514 }
515
516 /*
517 * This function is used to write data to the Master GW Data Descriptor.
518 * Data copied to the Master GW Data Descriptor MUST be shifted left so
519 * the data starts at the MSB of the descriptor registers as required by
520 * the underlying hardware. TYU_WRITE_DATA enables byte swapping when
521 * writing data bytes, and MUST be called by the SMBus write routines to
522 * copy data to the 32 * 32-bit HW Data registers a.k.a Master GW Data
523 * Descriptor.
524 */
525 static void mlxbf_i2c_write_data(void __iomem *io, int reg, u32 val)
526 {
> 527 mlxbf_i2c_write(io, reg, (u32)cpu_to_be32(val));
528 }
529
---
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: 39673 bytes --]
reply other threads:[~2020-10-12 13:11 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=202010122115.lA9XwEMl-lkp@intel.com \
--to=lkp@intel.com \
--cc=kblaiech@mellanox.com \
--cc=kbuild-all@lists.01.org \
--cc=linux-mm@kvack.org \
--cc=vadimp@mellanox.com \
--cc=wsa-dev@sang-engineering.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