From: kernel test robot <lkp@intel.com>
To: cros-kernel-buildreports@googlegroups.com
Cc: oe-kbuild-all@lists.linux.dev
Subject: [android-common:android17-6.18-p3s 27/27] drivers/iommu/arm/arm-smmu-v3/arm-smmu-v3.c:4649:34: sparse: sparse: symbol 'arm_smmu_aux_table' was not declared. Should it be static?
Date: Fri, 16 Oct 2026 14:20:32 +0200 [thread overview]
Message-ID: <202610161453.WF6iuaID-lkp@intel.com> (raw)
tree: https://android.googlesource.com/kernel/common android17-6.18-p3s
head: b4108abbd0e1cb0df40452dee77291f106e1d711
commit: 0bab644878595feedb839a62812e5116bb7acaa1 [27/27] FROMLIST: iommu/arm-smmu-v3: Support probing KVM emulated devices
config: arm64-randconfig-r2302-20261016 (https://download.01.org/0day-ci/archive/20261016/202610161453.WF6iuaID-lkp@intel.com/config)
compiler: aarch64-linux-gcc (GCC) 11.5.0
sparse: v0.6.5-rc1
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20261016/202610161453.WF6iuaID-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/202610161453.WF6iuaID-lkp@intel.com/
sparse warnings: (new ones prefixed by >>)
>> drivers/iommu/arm/arm-smmu-v3/arm-smmu-v3.c:4649:34: sparse: sparse: symbol 'arm_smmu_aux_table' was not declared. Should it be static?
>> drivers/iommu/arm/arm-smmu-v3/arm-smmu-v3.c:4654:25: sparse: sparse: symbol 'arm_smmu_driver_emu' was not declared. Should it be static?
drivers/iommu/arm/arm-smmu-v3/arm-smmu-v3.c: note: in included file (through arch/arm64/include/asm/atomic.h, include/linux/atomic.h, include/asm-generic/bitops/atomic.h, ...):
arch/arm64/include/asm/cmpxchg.h:168:1: sparse: sparse: cast truncates bits from constant value (ffffffff80000000 becomes 0)
arch/arm64/include/asm/cmpxchg.h:168:1: sparse: sparse: cast truncates bits from constant value (ffffffff80000000 becomes 0)
vim +/arm_smmu_aux_table +4649 drivers/iommu/arm/arm-smmu-v3/arm-smmu-v3.c
4648
> 4649 const struct auxiliary_device_id arm_smmu_aux_table[] = {
4650 { .name = "protected_kvm.smmu_v3_emu" },
4651 { },
4652 };
4653
> 4654 struct auxiliary_driver arm_smmu_driver_emu = {
4655 .name = "arm-smmu-v3-emu",
4656 .id_table = arm_smmu_aux_table,
4657 .probe = arm_smmu_device_probe_emu,
4658 .shutdown = arm_smmu_device_shutdown_emu,
4659 };
4660
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2026-10-16 12:21 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=202610161453.WF6iuaID-lkp@intel.com \
--to=lkp@intel.com \
--cc=cros-kernel-buildreports@googlegroups.com \
--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.