From: kernel test robot <lkp@intel.com>
To: Ken Raeburn <raeburn@redhat.com>
Cc: oe-kbuild-all@lists.linux.dev, linux-hwmon@vger.kernel.org,
Guenter Roeck <linux@roeck-us.net>,
Matthew Sakai <msakai@redhat.com>
Subject: [groeck-staging:testing 2/11] drivers/md/dm-vdo/murmurhash3.c:21:31: sparse: sparse: incorrect type in argument 1 (different base types)
Date: Mon, 1 Apr 2024 17:57:16 +0800 [thread overview]
Message-ID: <202404011734.OlyXtb2L-lkp@intel.com> (raw)
tree: https://git.kernel.org/pub/scm/linux/kernel/git/groeck/linux-staging.git testing
head: ad98b547d596561b6bdc5c2fdf8aa1a620c9e6fa
commit: af76a97d146976298a6fbd154dd39b6e9e321b73 [2/11] dm vdo: use kernel byteswapping routines instead of GCC ones
config: alpha-randconfig-r111-20240331 (https://download.01.org/0day-ci/archive/20240401/202404011734.OlyXtb2L-lkp@intel.com/config)
compiler: alpha-linux-gcc (GCC) 13.2.0
reproduce: (https://download.01.org/0day-ci/archive/20240401/202404011734.OlyXtb2L-lkp@intel.com/reproduce)
If you fix the issue in a separate patch/commit (i.e. not just a new version of
the same patch/commit), kindly add following tags
| Reported-by: kernel test robot <lkp@intel.com>
| Closes: https://lore.kernel.org/oe-kbuild-all/202404011734.OlyXtb2L-lkp@intel.com/
sparse warnings: (new ones prefixed by >>)
>> drivers/md/dm-vdo/murmurhash3.c:21:31: sparse: sparse: incorrect type in argument 1 (different base types) @@ expected restricted __le64 const [usertype] *p @@ got unsigned long long const [usertype] * @@
drivers/md/dm-vdo/murmurhash3.c:21:31: sparse: expected restricted __le64 const [usertype] *p
drivers/md/dm-vdo/murmurhash3.c:21:31: sparse: got unsigned long long const [usertype] *
>> drivers/md/dm-vdo/murmurhash3.c:21:31: sparse: sparse: incorrect type in argument 1 (different base types) @@ expected restricted __le64 const [usertype] *p @@ got unsigned long long const [usertype] * @@
drivers/md/dm-vdo/murmurhash3.c:21:31: sparse: expected restricted __le64 const [usertype] *p
drivers/md/dm-vdo/murmurhash3.c:21:31: sparse: got unsigned long long const [usertype] *
>> drivers/md/dm-vdo/murmurhash3.c:26:14: sparse: sparse: incorrect type in assignment (different base types) @@ expected unsigned long long [usertype] @@ got restricted __le64 [usertype] @@
drivers/md/dm-vdo/murmurhash3.c:26:14: sparse: expected unsigned long long [usertype]
drivers/md/dm-vdo/murmurhash3.c:26:14: sparse: got restricted __le64 [usertype]
>> drivers/md/dm-vdo/murmurhash3.c:26:14: sparse: sparse: incorrect type in assignment (different base types) @@ expected unsigned long long [usertype] @@ got restricted __le64 [usertype] @@
drivers/md/dm-vdo/murmurhash3.c:26:14: sparse: expected unsigned long long [usertype]
drivers/md/dm-vdo/murmurhash3.c:26:14: sparse: got restricted __le64 [usertype]
vim +21 drivers/md/dm-vdo/murmurhash3.c
17
18 #define ROTL64(x, y) rotl64(x, y)
19 static __always_inline u64 getblock64(const u64 *p, int i)
20 {
> 21 return le64_to_cpup(&p[i]);
22 }
23
24 static __always_inline void putblock64(u64 *p, int i, u64 value)
25 {
> 26 p[i] = cpu_to_le64(value);
27 }
28
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2024-04-01 9:57 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=202404011734.OlyXtb2L-lkp@intel.com \
--to=lkp@intel.com \
--cc=linux-hwmon@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=msakai@redhat.com \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=raeburn@redhat.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).