From: kernel test robot <lkp@intel.com>
To: Krzysztof Kozlowski <krzk@kernel.org>
Cc: kbuild-all@lists.01.org, netdev@vger.kernel.org
Subject: [net-next:master 469/495] drivers/nfc/fdp/fdp.c:116:67: sparse: sparse: incorrect type in argument 4 (different modifiers)
Date: Fri, 30 Jul 2021 04:06:42 +0800 [thread overview]
Message-ID: <202107300426.FDSTqdJt-lkp@intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 2855 bytes --]
tree: https://git.kernel.org/pub/scm/linux/kernel/git/davem/net-next.git master
head: 88ea96f8c14e39f7ee397b815de622ea5e1481ab
commit: 3d463dd5023b5a58b3c37207d65eeb5acbac2be3 [469/495] nfc: fdp: constify several pointers
config: ia64-randconfig-s032-20210728 (attached as .config)
compiler: ia64-linux-gcc (GCC) 10.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-341-g8af24329-dirty
# https://git.kernel.org/pub/scm/linux/kernel/git/davem/net-next.git/commit/?id=3d463dd5023b5a58b3c37207d65eeb5acbac2be3
git remote add net-next https://git.kernel.org/pub/scm/linux/kernel/git/davem/net-next.git
git fetch --no-tags net-next master
git checkout 3d463dd5023b5a58b3c37207d65eeb5acbac2be3
# save the attached .config to linux build tree
COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-10.3.0 make.cross C=1 CF='-fdiagnostic-prefix -D__CHECK_ENDIAN__' ARCH=ia64
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/nfc/fdp/fdp.c:116:67: sparse: sparse: incorrect type in argument 4 (different modifiers) @@ expected unsigned char [usertype] *payload @@ got char const *data @@
drivers/nfc/fdp/fdp.c:116:67: sparse: expected unsigned char [usertype] *payload
drivers/nfc/fdp/fdp.c:116:67: sparse: got char const *data
>> drivers/nfc/fdp/fdp.c:116:67: sparse: sparse: incorrect type in argument 4 (different modifiers) @@ expected unsigned char [usertype] *payload @@ got char const *data @@
drivers/nfc/fdp/fdp.c:116:67: sparse: expected unsigned char [usertype] *payload
drivers/nfc/fdp/fdp.c:116:67: sparse: got char const *data
vim +116 drivers/nfc/fdp/fdp.c
a06347c04c13e38 Robert Dolca 2015-10-22 112
a06347c04c13e38 Robert Dolca 2015-10-22 113 static inline int fdp_nci_set_production_data(struct nci_dev *ndev, u8 len,
3d463dd5023b5a5 Krzysztof Kozlowski 2021-07-29 114 const char *data)
a06347c04c13e38 Robert Dolca 2015-10-22 115 {
a06347c04c13e38 Robert Dolca 2015-10-22 @116 return nci_prop_cmd(ndev, NCI_OP_PROP_SET_PDATA_OID, len, data);
a06347c04c13e38 Robert Dolca 2015-10-22 117 }
a06347c04c13e38 Robert Dolca 2015-10-22 118
:::::: The code at line 116 was first introduced by commit
:::::: a06347c04c13e380afce0c9816df51f00b83faf1 NFC: Add Intel Fields Peak NFC solution driver
:::::: TO: Robert Dolca <robert.dolca@intel.com>
:::::: CC: Samuel Ortiz <sameo@linux.intel.com>
---
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: 32024 bytes --]
next reply other threads:[~2021-07-29 20:07 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-29 20:06 kernel test robot [this message]
2021-07-30 9:13 ` [net-next:master 469/495] drivers/nfc/fdp/fdp.c:116:67: sparse: sparse: incorrect type in argument 4 (different modifiers) Krzysztof Kozlowski
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=202107300426.FDSTqdJt-lkp@intel.com \
--to=lkp@intel.com \
--cc=kbuild-all@lists.01.org \
--cc=krzk@kernel.org \
--cc=netdev@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).