From: kernel test robot <lkp@intel.com>
To: Dan Williams <dan.j.williams@intel.com>
Cc: kbuild-all@lists.01.org,
Alison Schofield <alison.schofield@intel.com>,
Vishal Verma <vishal.l.verma@intel.com>,
Ira Weiny <ira.weiny@intel.com>,
Ben Widawsky <ben.widawsky@intel.com>,
Dan Williams <dan.j.williams@intel.com>,
linux-kernel@vger.kernel.org,
Jonathan Cameron <Jonathan.Cameron@huawei.com>
Subject: [cxl-cxl:pending 14/38] drivers/nvdimm/nd.h:67:26: sparse: sparse: cast to restricted __le32
Date: Sat, 14 Aug 2021 17:38:38 +0800 [thread overview]
Message-ID: <202108141729.8G4yM4pK-lkp@intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 2335 bytes --]
tree: https://git.kernel.org/pub/scm/linux/kernel/git/cxl/cxl.git pending
head: fa809cc6feedcd2575b63def7135dfaf066266bb
commit: a11d1b4adfef0134a49f00a1b7d2e7e7769a08b0 [14/38] libnvdimm/labels: Introduce label setter helpers
config: x86_64-randconfig-s021-20210814 (attached as .config)
compiler: gcc-9 (Debian 9.3.0-22) 9.3.0
reproduce:
# apt-get install sparse
# sparse version: v0.6.3-348-gf0e6938b-dirty
# https://git.kernel.org/pub/scm/linux/kernel/git/cxl/cxl.git/commit/?id=a11d1b4adfef0134a49f00a1b7d2e7e7769a08b0
git remote add cxl-cxl https://git.kernel.org/pub/scm/linux/kernel/git/cxl/cxl.git
git fetch --no-tags cxl-cxl pending
git checkout a11d1b4adfef0134a49f00a1b7d2e7e7769a08b0
# save the attached .config to linux build tree
make W=1 C=1 CF='-fdiagnostic-prefix -D__CHECK_ENDIAN__' O=build_dir ARCH=x86_64 SHELL=/bin/bash drivers/
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/nvdimm/label.c: note: in included file (through drivers/nvdimm/nd-core.h):
>> drivers/nvdimm/nd.h:67:26: sparse: sparse: cast to restricted __le32
>> drivers/nvdimm/nd.h:67:24: sparse: sparse: incorrect type in assignment (different base types) @@ expected restricted __le32 [usertype] slot @@ got unsigned int [usertype] @@
drivers/nvdimm/nd.h:67:24: sparse: expected restricted __le32 [usertype] slot
drivers/nvdimm/nd.h:67:24: sparse: got unsigned int [usertype]
>> drivers/nvdimm/nd.h:67:26: sparse: sparse: cast to restricted __le32
>> drivers/nvdimm/nd.h:67:24: sparse: sparse: incorrect type in assignment (different base types) @@ expected restricted __le32 [usertype] slot @@ got unsigned int [usertype] @@
drivers/nvdimm/nd.h:67:24: sparse: expected restricted __le32 [usertype] slot
drivers/nvdimm/nd.h:67:24: sparse: got unsigned int [usertype]
vim +67 drivers/nvdimm/nd.h
63
64 static inline void nsl_set_slot(struct nvdimm_drvdata *ndd,
65 struct nd_namespace_label *nd_label, u32 slot)
66 {
> 67 nd_label->slot = __le32_to_cpu(slot);
68 }
69
---
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: 38661 bytes --]
reply other threads:[~2021-08-14 9:39 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=202108141729.8G4yM4pK-lkp@intel.com \
--to=lkp@intel.com \
--cc=Jonathan.Cameron@huawei.com \
--cc=alison.schofield@intel.com \
--cc=ben.widawsky@intel.com \
--cc=dan.j.williams@intel.com \
--cc=ira.weiny@intel.com \
--cc=kbuild-all@lists.01.org \
--cc=linux-kernel@vger.kernel.org \
--cc=vishal.l.verma@intel.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