mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: Hari Bathini <hbathini@linux.ibm.com>
Cc: kbuild-all@lists.01.org, linux-kernel@vger.kernel.org,
	Michael Ellerman <mpe@ellerman.id.au>
Subject: arch/powerpc/platforms/powernv/opal-fadump.c:42:33: sparse: sparse: incorrect type in assignment (different base types)
Date: Sat, 8 Aug 2020 19:32:17 +0800	[thread overview]
Message-ID: <202008081913.R3c58O7u%lkp@intel.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 2981 bytes --]

tree:   https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
head:   449dc8c97089a6e09fb2dac4d92b1b7ac0eb7c1e
commit: 742a265accd3e3afcc8e7b17f409c93c1de8be85 powerpc/fadump: register kernel metadata address with opal
date:   11 months ago
config: powerpc64-randconfig-s032-20200808 (attached as .config)
compiler: powerpc64-linux-gcc (GCC) 9.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.2-118-ge1578773-dirty
        git checkout 742a265accd3e3afcc8e7b17f409c93c1de8be85
        # save the attached .config to linux build tree
        COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-9.3.0 make.cross C=1 CF='-fdiagnostic-prefix -D__CHECK_ENDIAN__' ARCH=powerpc64 

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 >>)

>> arch/powerpc/platforms/powernv/opal-fadump.c:42:33: sparse: sparse: incorrect type in assignment (different base types) @@     expected restricted __be64 [usertype] dest @@     got unsigned long long [usertype] addr @@
>> arch/powerpc/platforms/powernv/opal-fadump.c:42:33: sparse:     expected restricted __be64 [usertype] dest
>> arch/powerpc/platforms/powernv/opal-fadump.c:42:33: sparse:     got unsigned long long [usertype] addr
   arch/powerpc/platforms/powernv/opal-fadump.c:43:33: sparse: sparse: incorrect type in assignment (different base types) @@     expected restricted __be64 [usertype] size @@     got unsigned long boot_memory_size @@
>> arch/powerpc/platforms/powernv/opal-fadump.c:43:33: sparse:     expected restricted __be64 [usertype] size
   arch/powerpc/platforms/powernv/opal-fadump.c:43:33: sparse:     got unsigned long boot_memory_size
>> arch/powerpc/platforms/powernv/opal-fadump.c:50:53: sparse: sparse: restricted __be64 degrades to integer

vim +42 arch/powerpc/platforms/powernv/opal-fadump.c

    32	
    33	static u64 opal_fadump_init_mem_struct(struct fw_dump *fadump_conf)
    34	{
    35		u64 addr = fadump_conf->reserve_dump_area_start;
    36	
    37		opal_fdm = __va(fadump_conf->kernel_metadata);
    38		opal_fadump_init_metadata(opal_fdm);
    39	
    40		opal_fdm->region_cnt = 1;
    41		opal_fdm->rgn[0].src	= 0;
  > 42		opal_fdm->rgn[0].dest	= addr;
  > 43		opal_fdm->rgn[0].size	= fadump_conf->boot_memory_size;
    44		addr += fadump_conf->boot_memory_size;
    45	
    46		/*
    47		 * Kernel metadata is passed to f/w and retrieved in capture kerenl.
    48		 * So, use it to save fadump header address instead of calculating it.
    49		 */
  > 50		opal_fdm->fadumphdr_addr = (opal_fdm->rgn[0].dest +
    51					    fadump_conf->boot_memory_size);
    52	
    53		return addr;
    54	}
    55	

---
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: 30345 bytes --]

                 reply	other threads:[~2020-08-08 11:40 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=202008081913.R3c58O7u%lkp@intel.com \
    --to=lkp@intel.com \
    --cc=hbathini@linux.ibm.com \
    --cc=kbuild-all@lists.01.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mpe@ellerman.id.au \
    /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

all inboxes | Powered by JetHome®