From: kernel test robot <lkp@intel.com>
To: Sudeep Holla <sudeep.holla@kernel.org>
Cc: oe-kbuild-all@lists.linux.dev, Yeoreum Yun <yeoreum.yun@arm.com>,
Suzuki K Poulose <suzuki.poulose@arm.com>
Subject: [sudeep-holla:for-next/arm_fw/updates 2/2] drivers/firmware/arm/smccc/smccc.c:21:21: sparse: sparse: symbol 'smccc_soc_id_version' was not declared. Should it be static?
Date: Mon, 09 Nov 2026 20:37:43 +0100 [thread overview]
Message-ID: <202611092008.peLqOBq7-lkp@intel.com> (raw)
Hi Sudeep,
First bad commit (maybe != root cause):
tree: https://git.kernel.org/pub/scm/linux/kernel/git/sudeep.holla/linux.git for-next/arm_fw/updates
head: 49c49ca0c4d02848a9576f72c4741c38c5ba09de
commit: 49c49ca0c4d02848a9576f72c4741c38c5ba09de [2/2] firmware: arm: Group interface drivers under arm/
config: arm64-randconfig-r2311-20261109 (https://download.01.org/0day-ci/archive/20261109/202611092008.peLqOBq7-lkp@intel.com/config)
compiler: aarch64-linux-gcc (GCC) 15.3.0
sparse: v0.6.5-rc1-21-g84ec0658
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20261109/202611092008.peLqOBq7-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/202611092008.peLqOBq7-lkp@intel.com/
sparse warnings: (new ones prefixed by >>)
>> drivers/firmware/arm/smccc/smccc.c:21:21: sparse: sparse: symbol 'smccc_soc_id_version' was not declared. Should it be static?
>> drivers/firmware/arm/smccc/smccc.c:22:21: sparse: sparse: symbol 'smccc_soc_id_revision' was not declared. Should it be static?
vim +/smccc_soc_id_version +21 drivers/firmware/arm/smccc/smccc.c
f2ae97062a48b1 drivers/firmware/smccc/smccc.c Sudeep Holla 2020-05-18 19
a37e31fc97efe7 drivers/firmware/smccc/smccc.c Andre Przywara 2021-01-06 20 bool __ro_after_init smccc_trng_available = false;
35727af2b15d98 drivers/firmware/smccc/smccc.c Shanker Donthineni 2023-03-18 @21 s32 __ro_after_init smccc_soc_id_version = SMCCC_RET_NOT_SUPPORTED;
35727af2b15d98 drivers/firmware/smccc/smccc.c Shanker Donthineni 2023-03-18 @22 s32 __ro_after_init smccc_soc_id_revision = SMCCC_RET_NOT_SUPPORTED;
a37e31fc97efe7 drivers/firmware/smccc/smccc.c Andre Przywara 2021-01-06 23
:::::: The code at line 21 was first introduced by commit
:::::: 35727af2b15d98a2dd2811d631d3a3886111312e irqchip/gicv3: Workaround for NVIDIA erratum T241-FABRIC-4
:::::: TO: Shanker Donthineni <sdonthineni@nvidia.com>
:::::: CC: Marc Zyngier <maz@kernel.org>
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2026-11-09 19:38 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=202611092008.peLqOBq7-lkp@intel.com \
--to=lkp@intel.com \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=sudeep.holla@kernel.org \
--cc=suzuki.poulose@arm.com \
--cc=yeoreum.yun@arm.com \
/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.