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:43:5: sparse: sparse: symbol 'pcie_port_size' was not declared. Should it be static?
Date: Sat, 12 Oct 2024 17:52:21 +0800 [thread overview]
Message-ID: <202410121730.ViWfi0F2-lkp@intel.com> (raw)
tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
head: 09f6b0c8904bfaa1e0601bc102e1b6aa6de8c98f
commit: e2fe85aa6a6387c4babe4c191e50b7af8ee37faf ARM: mv78xx0: un-deprecate Terastation WXL
date: 1 year, 9 months ago
config: arm-randconfig-r122-20241012 (https://download.01.org/0day-ci/archive/20241012/202410121730.ViWfi0F2-lkp@intel.com/config)
compiler: arm-linux-gnueabi-gcc (GCC) 14.1.0
reproduce: (https://download.01.org/0day-ci/archive/20241012/202410121730.ViWfi0F2-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/202410121730.ViWfi0F2-lkp@intel.com/
sparse warnings: (new ones prefixed by >>)
>> arch/arm/mach-mv78xx0/pcie.c:43:5: sparse: sparse: symbol 'pcie_port_size' was not declared. Should it be static?
vim +/pcie_port_size +43 arch/arm/mach-mv78xx0/pcie.c
cfdeb6376e439c Lennert Buytenhek 2009-02-20 42
0b9b18e0166d89 Rob Herring 2012-07-09 @43 u32 pcie_port_size[8] = {
0b9b18e0166d89 Rob Herring 2012-07-09 44 0,
0b9b18e0166d89 Rob Herring 2012-07-09 45 0x30000000,
0b9b18e0166d89 Rob Herring 2012-07-09 46 0x10000000,
0b9b18e0166d89 Rob Herring 2012-07-09 47 0x10000000,
0b9b18e0166d89 Rob Herring 2012-07-09 48 0x08000000,
0b9b18e0166d89 Rob Herring 2012-07-09 49 0x08000000,
0b9b18e0166d89 Rob Herring 2012-07-09 50 0x08000000,
0b9b18e0166d89 Rob Herring 2012-07-09 51 0x04000000,
0b9b18e0166d89 Rob Herring 2012-07-09 52 };
0b9b18e0166d89 Rob Herring 2012-07-09 53
:::::: The code at line 43 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-10-12 9:53 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=202410121730.ViWfi0F2-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 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.