From: Robin Murphy <robin.murphy@arm.com>
To: Ashish Mhetre <amhetre@nvidia.com>, will@kernel.org, nicolinc@nvidia.com
Cc: llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev,
thierry.reding@gmail.com, jonathanh@nvidia.com,
vdumpa@nvidia.com, jgg@ziepe.ca,
linux-arm-kernel@lists.infradead.org, iommu@lists.linux.dev,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-tegra@vger.kernel.org, conor+dt@kernel.org,
krzk+dt@kernel.org, joro@8bytes.org, robh@kernel.org,
kernel test robot <lkp@intel.com>
Subject: Re: [PATCH V3 1/3] iommu/arm-smmu-v3: Add device-tree support for CMDQV driver
Date: Wed, 3 Dec 2025 15:49:31 +0000 [thread overview]
Message-ID: <a917aded-4404-4b63-8d2c-96aa8b84f81f@arm.com> (raw)
In-Reply-To: <47684b91-7c0f-4260-abfd-2795fdaa2b31@nvidia.com>
On 2025-12-03 11:04 am, Ashish Mhetre wrote:
>
> On 12/3/2025 2:05 PM, kernel test robot wrote:
>> External email: Use caution opening links or attachments
>>
>>
>> Hi Ashish,
>>
>> kernel test robot noticed the following build errors:
>>
>> [auto build test ERROR on next-20251201]
>> [also build test ERROR on v6.18]
>> [cannot apply to robh/for-next linus/master v6.18 v6.18-rc7 v6.18-rc6]
>> [If your patch is applied to the wrong git tree, kindly drop us a note.
>> And when submitting patch, we suggest to use '--base' as documented in
>> https://git-scm.com/docs/git-format-patch#_base_tree_information]
>>
>> url: https://github.com/intel-lab-lkp/linux/commits/Ashish-Mhetre/
>> iommu-arm-smmu-v3-Add-device-tree-support-for-CMDQV-
>> driver/20251202-003517
>> base: next-20251201
>> patch link: https://lore.kernel.org/r/20251201163219.3237266-2-
>> amhetre%40nvidia.com
>> patch subject: [PATCH V3 1/3] iommu/arm-smmu-v3: Add device-tree
>> support for CMDQV driver
>> config: arm64-allmodconfig (https://download.01.org/0day-ci/
>> archive/20251203/202512031601.IpliwbHW-lkp@intel.com/config)
>> compiler: clang version 19.1.7 (https://github.com/llvm/llvm-project
>> cd708029e0b2869e80abe31ddb175f7c35361f90)
>> reproduce (this is a W=1 build): (https://download.01.org/0day-ci/
>> archive/20251203/202512031601.IpliwbHW-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/202512031601.IpliwbHW-
>> lkp@intel.com/
>>
>> All errors (new ones prefixed by >>):
>>
>>>> ld.lld: error: duplicate symbol: init_module
>> >>> defined at arm-smmu-v3.c
>> >>> drivers/iommu/arm/arm-smmu-v3/arm-smmu-v3.o:
>> (init_module)
>> >>> defined at tegra241-cmdqv.c
>> >>> drivers/iommu/arm/arm-smmu-v3/tegra241-cmdqv.o:
>> (.init.text+0x4)
>> --
>>>> ld.lld: error: duplicate symbol: cleanup_module
>> >>> defined at arm-smmu-v3.c
>> >>> drivers/iommu/arm/arm-smmu-v3/arm-smmu-v3.o:
>> (cleanup_module)
>> >>> defined at tegra241-cmdqv.c
>> >>> drivers/iommu/arm/arm-smmu-v3/tegra241-cmdqv.o:
>> (.exit.text+0x4)
>
> Hi Nic, Robin,
>
> How do you suggest fixing this? Is it fine to compile tegra241-cmdqv as
> separate module
> and export tegra241_cmdqv_probe() to fix this warning?
As Jon just pointed out, the issue is using module_platform_driver(),
which is unnecessary anyway since this is not a driver; nor is it even a
module, it's just some extra code that can be included in the
arm_smmu_v3 driver, and will be integral to the arm_smmu_v3.ko module if
built as a such.
You could sanity-check the compatible of the phandle target in
tegra_cmdqv_dt_probe() if you feel like you should do more than just
blindly trust the DT, but either way trying to register a dummy platform
driver that won't bind to anything is pointless.
> I am using GCC compiler and was not able to reproduce this with W=1 build.
This will be happening with CONFIG_ARM_SMMU_V3=m.
Thanks,
Robin.
>
> Thanks,
> Ashish Mhetre
>
>> --
>> 0-DAY CI Kernel Test Service
>> https://github.com/intel/lkp-tests/wiki
next prev parent reply other threads:[~2025-12-03 15:49 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-01 16:32 [PATCH V3 0/3] Add device tree support for NVIDIA Tegra CMDQV Ashish Mhetre
2025-12-01 16:32 ` [PATCH V3 1/3] iommu/arm-smmu-v3: Add device-tree support for CMDQV driver Ashish Mhetre
2025-12-03 8:35 ` kernel test robot
2025-12-03 11:04 ` Ashish Mhetre
2025-12-03 15:49 ` Robin Murphy [this message]
2025-12-05 6:15 ` Ashish Mhetre
2025-12-03 15:34 ` Jon Hunter
2025-12-01 16:32 ` [PATCH V3 2/3] dt-bindings: iommu: Add NVIDIA Tegra CMDQV support Ashish Mhetre
2025-12-04 21:28 ` Rob Herring (Arm)
2025-12-01 16:32 ` [PATCH V3 3/3] arm64: dts: nvidia: Add nodes for CMDQV Ashish Mhetre
2025-12-03 10:44 ` Jon Hunter
2025-12-03 11:06 ` Ashish Mhetre
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=a917aded-4404-4b63-8d2c-96aa8b84f81f@arm.com \
--to=robin.murphy@arm.com \
--cc=amhetre@nvidia.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=iommu@lists.linux.dev \
--cc=jgg@ziepe.ca \
--cc=jonathanh@nvidia.com \
--cc=joro@8bytes.org \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=lkp@intel.com \
--cc=llvm@lists.linux.dev \
--cc=nicolinc@nvidia.com \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=robh@kernel.org \
--cc=thierry.reding@gmail.com \
--cc=vdumpa@nvidia.com \
--cc=will@kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).