public inbox for [email protected]
 help / color / mirror / Atom feed
From: kernel test robot <[email protected]>
To: "Jason A. Donenfeld" <[email protected]>
Cc: [email protected], Ammar Faizi <[email protected]>,
	GNU/Weeb Mailing List <[email protected]>,
	[email protected]
Subject: [ammarfaizi2-block:crng/random/jd/smbios 2/3] drivers/firmware/dmi_scan.c:806:34: sparse: sparse: incorrect type in initializer (different address spaces)
Date: Sat, 17 Sep 2022 13:17:47 +0800	[thread overview]
Message-ID: <[email protected]> (raw)

tree:   https://github.com/ammarfaizi2/linux-block crng/random/jd/smbios
head:   1f282c3a5674aced9c26d319587135cd0f40ad38
commit: 00ee8ad7ad1c02fa8280c0e609b000fad782f348 [2/3] firmware: dmi: only add dmi buffer to rng once
config: ia64-randconfig-s032-20220916 (https://download.01.org/0day-ci/archive/20220917/[email protected]/config)
compiler: ia64-linux-gcc (GCC) 12.1.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.4-39-gce1a6720-dirty
        # https://github.com/ammarfaizi2/linux-block/commit/00ee8ad7ad1c02fa8280c0e609b000fad782f348
        git remote add ammarfaizi2-block https://github.com/ammarfaizi2/linux-block
        git fetch --no-tags ammarfaizi2-block crng/random/jd/smbios
        git checkout 00ee8ad7ad1c02fa8280c0e609b000fad782f348
        # save the config file
        mkdir build_dir && cp config build_dir/.config
        COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-12.1.0 make.cross C=1 CF='-fdiagnostic-prefix -D__CHECK_ENDIAN__' O=build_dir ARCH=ia64 SHELL=/bin/bash drivers/firmware/

If you fix the issue, kindly add following tag where applicable
Reported-by: kernel test robot <[email protected]>

sparse warnings: (new ones prefixed by >>)
   drivers/firmware/dmi_scan.c:143:13: sparse: sparse: incorrect type in assignment (different address spaces) @@     expected unsigned char [usertype] *buf @@     got void [noderef] __iomem * @@
   drivers/firmware/dmi_scan.c:143:13: sparse:     expected unsigned char [usertype] *buf
   drivers/firmware/dmi_scan.c:143:13: sparse:     got void [noderef] __iomem *
   drivers/firmware/dmi_scan.c:149:9: sparse: sparse: incorrect type in argument 1 (different address spaces) @@     expected void volatile [noderef] __iomem *addr @@     got unsigned char [usertype] *buf @@
   drivers/firmware/dmi_scan.c:149:9: sparse:     expected void volatile [noderef] __iomem *addr
   drivers/firmware/dmi_scan.c:149:9: sparse:     got unsigned char [usertype] *buf
   drivers/firmware/dmi_scan.c:774:19: sparse: sparse: incorrect type in assignment (different address spaces) @@     expected unsigned char [usertype] *dmi_table @@     got void [noderef] __iomem * @@
   drivers/firmware/dmi_scan.c:774:19: sparse:     expected unsigned char [usertype] *dmi_table
   drivers/firmware/dmi_scan.c:774:19: sparse:     got void [noderef] __iomem *
   drivers/firmware/dmi_scan.c:793:19: sparse: sparse: incorrect type in argument 1 (different address spaces) @@     expected void volatile [noderef] __iomem *addr @@     got unsigned char [usertype] *dmi_table @@
   drivers/firmware/dmi_scan.c:793:19: sparse:     expected void volatile [noderef] __iomem *addr
   drivers/firmware/dmi_scan.c:793:19: sparse:     got unsigned char [usertype] *dmi_table
>> drivers/firmware/dmi_scan.c:806:34: sparse: sparse: incorrect type in initializer (different address spaces) @@     expected unsigned char [usertype] *buf @@     got void [noderef] __iomem * @@
   drivers/firmware/dmi_scan.c:806:34: sparse:     expected unsigned char [usertype] *buf
   drivers/firmware/dmi_scan.c:806:34: sparse:     got void [noderef] __iomem *
   drivers/firmware/dmi_scan.c:811:9: sparse: sparse: incorrect type in argument 1 (different address spaces) @@     expected void volatile [noderef] __iomem *addr @@     got unsigned char [usertype] *buf @@
   drivers/firmware/dmi_scan.c:811:9: sparse:     expected void volatile [noderef] __iomem *addr
   drivers/firmware/dmi_scan.c:811:9: sparse:     got unsigned char [usertype] *buf
   drivers/firmware/dmi_scan.c:1118:13: sparse: sparse: incorrect type in assignment (different address spaces) @@     expected unsigned char [usertype] *buf @@     got void [noderef] __iomem * @@
   drivers/firmware/dmi_scan.c:1118:13: sparse:     expected unsigned char [usertype] *buf
   drivers/firmware/dmi_scan.c:1118:13: sparse:     got void [noderef] __iomem *
   drivers/firmware/dmi_scan.c:1124:19: sparse: sparse: incorrect type in argument 1 (different address spaces) @@     expected void volatile [noderef] __iomem *addr @@     got unsigned char [usertype] *buf @@
   drivers/firmware/dmi_scan.c:1124:19: sparse:     expected void volatile [noderef] __iomem *addr
   drivers/firmware/dmi_scan.c:1124:19: sparse:     got unsigned char [usertype] *buf

vim +806 drivers/firmware/dmi_scan.c

   803	
   804	static void __init dmi_random_walk(void)
   805	{
 > 806		u8 *buf = dmi_early_remap(dmi_base, dmi_len);
   807		if (buf == NULL)
   808			return;
   809	
   810		add_device_randomness(buf, dmi_len);
   811		dmi_early_unmap(buf, dmi_len);
   812	}
   813	

-- 
0-DAY CI Kernel Test Service
https://01.org/lkp

                 reply	other threads:[~2022-09-17  5: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 \
    [email protected] \
    [email protected] \
    [email protected] \
    [email protected] \
    [email protected] \
    [email protected] \
    [email protected] \
    /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