public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: Krzysztof Kozlowski <krzk@kernel.org>
Cc: oe-kbuild-all@lists.linux.dev, linux-kernel@vger.kernel.org,
	Dinh Nguyen <dinguyen@kernel.org>
Subject: drivers/edac/altera_edac.c:886:28: sparse: sparse: incorrect type in argument 1 (different base types)
Date: Fri, 13 Sep 2024 14:21:28 +0800	[thread overview]
Message-ID: <202409131434.roYJxLGs-lkp@intel.com> (raw)

tree:   https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
head:   196145c606d0f816fd3926483cb1ff87e09c2c0b
commit: 4a9a1a5602d82c079325bf37466af0b67d6c0b9e arm64: socfpga: merge Agilex and N5X into ARCH_INTEL_SOCFPGA
date:   3 years, 6 months ago
config: arm64-randconfig-r111-20240913 (https://download.01.org/0day-ci/archive/20240913/202409131434.roYJxLGs-lkp@intel.com/config)
compiler: aarch64-linux-gcc (GCC) 14.1.0
reproduce: (https://download.01.org/0day-ci/archive/20240913/202409131434.roYJxLGs-lkp@intel.com/reproduce)

If you fix the issue in a separate patch/commit (i.e. not just a new version of
the same patch/commit), kindly add following tags
| Reported-by: kernel test robot <lkp@intel.com>
| Closes: https://lore.kernel.org/oe-kbuild-all/202409131434.roYJxLGs-lkp@intel.com/

sparse warnings: (new ones prefixed by >>)
>> drivers/edac/altera_edac.c:886:28: sparse: sparse: incorrect type in argument 1 (different base types) @@     expected restricted __be32 const [usertype] *p @@     got unsigned int const [usertype] *handle @@
   drivers/edac/altera_edac.c:886:28: sparse:     expected restricted __be32 const [usertype] *p
   drivers/edac/altera_edac.c:886:28: sparse:     got unsigned int const [usertype] *handle

vim +886 drivers/edac/altera_edac.c

1166fde93d5b1d Thor Thayer 2016-06-22  878  
1166fde93d5b1d Thor Thayer 2016-06-22  879  static inline int a10_get_irq_mask(struct device_node *np)
1166fde93d5b1d Thor Thayer 2016-06-22  880  {
1166fde93d5b1d Thor Thayer 2016-06-22  881  	int irq;
1166fde93d5b1d Thor Thayer 2016-06-22  882  	const u32 *handle = of_get_property(np, "interrupts", NULL);
1166fde93d5b1d Thor Thayer 2016-06-22  883  
1166fde93d5b1d Thor Thayer 2016-06-22  884  	if (!handle)
1166fde93d5b1d Thor Thayer 2016-06-22  885  		return -ENODEV;
1166fde93d5b1d Thor Thayer 2016-06-22 @886  	irq = be32_to_cpup(handle);
1166fde93d5b1d Thor Thayer 2016-06-22  887  	return irq;
1166fde93d5b1d Thor Thayer 2016-06-22  888  }
1166fde93d5b1d Thor Thayer 2016-06-22  889  

:::::: The code at line 886 was first introduced by commit
:::::: 1166fde93d5b1d7267992edc7e2c8ee129d6667e EDAC, altera: Add Arria10 ECC memory init functions

:::::: TO: Thor Thayer <tthayer@opensource.altera.com>
:::::: CC: Borislav Petkov <bp@suse.de>

-- 
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki

             reply	other threads:[~2024-09-13  6:21 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-09-13  6:21 kernel test robot [this message]
  -- strict thread matches above, loose matches on Subject: below --
2022-10-17  7:04 drivers/edac/altera_edac.c:886:28: sparse: sparse: incorrect type in argument 1 (different base types) kernel test robot
2022-09-10 23:09 kernel test robot
2022-02-21  0:49 kernel test robot

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=202409131434.roYJxLGs-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=dinguyen@kernel.org \
    --cc=krzk@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=oe-kbuild-all@lists.linux.dev \
    /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