From: kernel test robot <lkp@intel.com>
To: Arnd Bergmann <arnd@arndb.de>
Cc: oe-kbuild-all@lists.linux.dev, linux-kernel@vger.kernel.org
Subject: arch/arm/mach-mv78xx0/pcie.c:46:5: sparse: sparse: symbol 'pcie_port_size' was not declared. Should it be static?
Date: Thu, 28 Nov 2024 06:23:45 +0800 [thread overview]
Message-ID: <202411280649.ZlacdSn2-lkp@intel.com> (raw)
tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
head: 7d4050728c83aa63828494ad0f4d0eb4faf5f97a
commit: 7036440eab3e2d47a775d4616909f8235488d714 ARM: omap1: enable multiplatform
date: 2 years, 6 months ago
config: arm-randconfig-r131-20241123 (https://download.01.org/0day-ci/archive/20241128/202411280649.ZlacdSn2-lkp@intel.com/config)
compiler: clang version 20.0.0git (https://github.com/llvm/llvm-project 592c0fe55f6d9a811028b5f3507be91458ab2713)
reproduce: (https://download.01.org/0day-ci/archive/20241128/202411280649.ZlacdSn2-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/202411280649.ZlacdSn2-lkp@intel.com/
sparse warnings: (new ones prefixed by >>)
>> arch/arm/mach-mv78xx0/pcie.c:46:5: sparse: sparse: symbol 'pcie_port_size' was not declared. Should it be static?
--
>> drivers/irqchip/irq-davinci-cp-intc.c:166:13: sparse: sparse: incorrect type in assignment (different address spaces) @@ expected void [noderef] __iomem *req @@ got struct resource * @@
drivers/irqchip/irq-davinci-cp-intc.c:166:13: sparse: expected void [noderef] __iomem *req
drivers/irqchip/irq-davinci-cp-intc.c:166:13: sparse: got struct resource *
vim +/pcie_port_size +46 arch/arm/mach-mv78xx0/pcie.c
cfdeb6376e439c5 Lennert Buytenhek 2009-02-20 45
0b9b18e0166d892 Rob Herring 2012-07-09 @46 u32 pcie_port_size[8] = {
0b9b18e0166d892 Rob Herring 2012-07-09 47 0,
0b9b18e0166d892 Rob Herring 2012-07-09 48 0x30000000,
0b9b18e0166d892 Rob Herring 2012-07-09 49 0x10000000,
0b9b18e0166d892 Rob Herring 2012-07-09 50 0x10000000,
0b9b18e0166d892 Rob Herring 2012-07-09 51 0x08000000,
0b9b18e0166d892 Rob Herring 2012-07-09 52 0x08000000,
0b9b18e0166d892 Rob Herring 2012-07-09 53 0x08000000,
0b9b18e0166d892 Rob Herring 2012-07-09 54 0x04000000,
0b9b18e0166d892 Rob Herring 2012-07-09 55 };
0b9b18e0166d892 Rob Herring 2012-07-09 56
:::::: The code at line 46 was first introduced by commit
:::::: 0b9b18e0166d8925ed222335efbc3cfd66aa882f ARM: mv78xx0: use fixed pci i/o mapping
:::::: TO: Rob Herring <rob.herring@calxeda.com>
:::::: CC: Rob Herring <rob.herring@calxeda.com>
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2024-11-27 22:24 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=202411280649.ZlacdSn2-lkp@intel.com \
--to=lkp@intel.com \
--cc=arnd@arndb.de \
--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