From: kernel test robot <lkp@intel.com>
To: cros-kernel-buildreports@googlegroups.com
Cc: oe-kbuild-all@lists.linux.dev
Subject: [android-common:android16-6.12-p3s 1/1] arch/arm64/kvm/hyp/nvhe/iommu/iommu.c:322:9: error: implicit declaration of function '_iommu_iotlb_add_page'; did you mean 'iommu_iotlb_gather_add_page'?
Date: Fri, 30 Oct 2026 07:16:15 +0100 [thread overview]
Message-ID: <202610300753.NDLI2Tec-lkp@intel.com> (raw)
Hi Mostafa,
FYI, the error/warning still remains.
tree: https://android.googlesource.com/kernel/common android16-6.12-p3s
head: 19f89117d8d335493422e7d44b06d1cd97f0279a
commit: 561f9e328538b6f1abb7b17faae3db6505172925 [1/1] BACKPORT: FROMLIST: KVM: arm64: iommu: support iommu_iotlb_gather
config: arm64-randconfig-r2108-20261030 (https://download.01.org/0day-ci/archive/20261030/202610300753.NDLI2Tec-lkp@intel.com/config)
compiler: aarch64-linux-gcc (GCC) 12.5.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20261030/202610300753.NDLI2Tec-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/202610300753.NDLI2Tec-lkp@intel.com/
All errors (new ones prefixed by >>):
arch/arm64/kvm/hyp/nvhe/iommu/iommu.c: In function 'kvm_iommu_iotlb_gather_add_page':
>> arch/arm64/kvm/hyp/nvhe/iommu/iommu.c:322:9: error: implicit declaration of function '_iommu_iotlb_add_page'; did you mean 'iommu_iotlb_gather_add_page'? [-Werror=implicit-function-declaration]
322 | _iommu_iotlb_add_page(domain, gather, iova, size, kvm_iommu_iotlb_sync);
| ^~~~~~~~~~~~~~~~~~~~~
| iommu_iotlb_gather_add_page
cc1: some warnings being treated as errors
Kconfig warnings: (for reference only)
WARNING: unmet direct dependencies detected for USB_PHY
Depends on [n]: USB_SUPPORT [=n]
Selected by [y]:
- GKI_HIDDEN_USB_CONFIGS [=y] && 64BIT [=y]
WARNING: unmet direct dependencies detected for DRM_MIPI_DSI
Depends on [n]: HAS_IOMEM [=y] && DRM [=n]
Selected by [y]:
- GKI_HIDDEN_DRM_CONFIGS [=y] && 64BIT [=y]
vim +322 arch/arm64/kvm/hyp/nvhe/iommu/iommu.c
316
317 void kvm_iommu_iotlb_gather_add_page(struct kvm_hyp_iommu_domain *domain,
318 struct iommu_iotlb_gather *gather,
319 unsigned long iova,
320 size_t size)
321 {
> 322 _iommu_iotlb_add_page(domain, gather, iova, size, kvm_iommu_iotlb_sync);
323 }
324
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2026-10-30 6:16 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=202610300753.NDLI2Tec-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.