From: kernel test robot <lkp@intel.com>
To: kbuild-all@lists.01.org
Subject: [intel-linux-intel-lts:5.4/yocto 1363/10971] drivers/usb/typec/ucsi/ucsi_acpi.c:54:9: sparse: sparse: incorrect type in argument 2 (different address spaces)
Date: Wed, 16 Sep 2020 15:18:52 +0800 [thread overview]
Message-ID: <202009161550.k29zpNlb%lkp@intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 2690 bytes --]
tree: https://github.com/intel/linux-intel-lts.git 5.4/yocto
head: d3e34fac5e7582733593530aea91df73bfbcdef2
commit: 29e00c15f4cc490b222c2d03b2ee800ecf2d925f [1363/10971] usb: typec: ucsi: acpi: Move to the new API
config: x86_64-randconfig-s021-20200916 (attached as .config)
compiler: gcc-9 (Debian 9.3.0-15) 9.3.0
reproduce:
# apt-get install sparse
# sparse version: v0.6.2-201-g24bdaac6-dirty
git checkout 29e00c15f4cc490b222c2d03b2ee800ecf2d925f
# save the attached .config to linux build tree
make W=1 C=1 CF='-fdiagnostic-prefix -D__CHECK_ENDIAN__' ARCH=x86_64
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/usb/typec/ucsi/ucsi_acpi.c:54:9: sparse: sparse: incorrect type in argument 2 (different address spaces) @@ expected void const *from @@ got void [noderef] <asn:2> * @@
>> drivers/usb/typec/ucsi/ucsi_acpi.c:54:9: sparse: expected void const *from
drivers/usb/typec/ucsi/ucsi_acpi.c:54:9: sparse: got void [noderef] <asn:2> *
>> drivers/usb/typec/ucsi/ucsi_acpi.c:64:9: sparse: sparse: incorrect type in argument 1 (different address spaces) @@ expected void *to @@ got void [noderef] <asn:2> * @@
>> drivers/usb/typec/ucsi/ucsi_acpi.c:64:9: sparse: expected void *to
drivers/usb/typec/ucsi/ucsi_acpi.c:64:9: sparse: got void [noderef] <asn:2> *
# https://github.com/intel/linux-intel-lts/commit/29e00c15f4cc490b222c2d03b2ee800ecf2d925f
git remote add intel-linux-intel-lts https://github.com/intel/linux-intel-lts.git
git fetch --no-tags intel-linux-intel-lts 5.4/yocto
git checkout 29e00c15f4cc490b222c2d03b2ee800ecf2d925f
vim +54 drivers/usb/typec/ucsi/ucsi_acpi.c
43
44 static int ucsi_acpi_read(struct ucsi *ucsi, unsigned int offset,
45 void *val, size_t val_len)
46 {
47 struct ucsi_acpi *ua = ucsi_get_drvdata(ucsi);
48 int ret;
49
50 ret = ucsi_acpi_dsm(ua, UCSI_DSM_FUNC_READ);
51 if (ret)
52 return ret;
53
> 54 memcpy(val, ua->base + offset, val_len);
55
56 return 0;
57 }
58
59 static int ucsi_acpi_async_write(struct ucsi *ucsi, unsigned int offset,
60 const void *val, size_t val_len)
61 {
62 struct ucsi_acpi *ua = ucsi_get_drvdata(ucsi);
63
> 64 memcpy(ua->base + offset, val, val_len);
65
66 return ucsi_acpi_dsm(ua, UCSI_DSM_FUNC_WRITE);
67 }
68
---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all(a)lists.01.org
[-- Attachment #2: config.gz --]
[-- Type: application/gzip, Size: 31362 bytes --]
reply other threads:[~2020-09-16 7:18 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=202009161550.k29zpNlb%lkp@intel.com \
--to=lkp@intel.com \
--cc=kbuild-all@lists.01.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.