From: kernel test robot <lkp@intel.com>
To: Thierry Reding <treding@nvidia.com>
Cc: kbuild-all@lists.01.org,
Linux Memory Management List <linux-mm@kvack.org>,
Krzysztof Kozlowski <krzk@kernel.org>
Subject: [linux-next:master 7934/13550] arm-smmu-nvidia.c:undefined reference to `tegra_mc_probe_device'
Date: Mon, 28 Jun 2021 07:12:19 +0800 [thread overview]
Message-ID: <202106280715.lqSO4ypj-lkp@intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1434 bytes --]
tree: https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master
head: 8702f95941c215501826ea8743a8b64b83479209
commit: 8eb68595475ac5fcaaa3718a173283df48cb4ef1 [7934/13550] iommu/arm-smmu: tegra: Implement SID override programming
config: x86_64-randconfig-r013-20210628 (attached as .config)
compiler: gcc-9 (Debian 9.3.0-22) 9.3.0
reproduce (this is a W=1 build):
# https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/?id=8eb68595475ac5fcaaa3718a173283df48cb4ef1
git remote add linux-next https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git
git fetch --no-tags linux-next master
git checkout 8eb68595475ac5fcaaa3718a173283df48cb4ef1
# save the attached .config to linux build tree
mkdir build_dir
make W=1 O=build_dir ARCH=x86_64 SHELL=/bin/bash
If you fix the issue, kindly add following tag as appropriate
Reported-by: kernel test robot <lkp@intel.com>
Note: the linux-next/master HEAD 8702f95941c215501826ea8743a8b64b83479209 builds fine.
It may have been fixed somewhere.
All errors (new ones prefixed by >>):
ld: drivers/iommu/arm/arm-smmu/arm-smmu-nvidia.o: in function `nvidia_smmu_probe_finalize':
>> arm-smmu-nvidia.c:(.text+0x359): undefined reference to `tegra_mc_probe_device'
---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all@lists.01.org
[-- Attachment #2: .config.gz --]
[-- Type: application/gzip, Size: 40340 bytes --]
reply other threads:[~2021-06-27 23:12 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=202106280715.lqSO4ypj-lkp@intel.com \
--to=lkp@intel.com \
--cc=kbuild-all@lists.01.org \
--cc=krzk@kernel.org \
--cc=linux-mm@kvack.org \
--cc=treding@nvidia.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox