From: kernel test robot <lkp@intel.com>
To: Ankit Soni <Ankit.Soni@amd.com>, iommu@lists.linux.dev
Cc: llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev,
vasant.hegde@amd.com, suravee.suthikulpanit@amd.com,
joro@8bytes.org, will@kernel.org, robin.murphy@arm.com,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] iommu/amd: Adhere to IVINFO[VASIZE] for address limits
Date: Sat, 28 Feb 2026 18:56:01 +0800 [thread overview]
Message-ID: <202602281837.QQl5six6-lkp@intel.com> (raw)
In-Reply-To: <cf1a1e3d96c3571ac5caa528caa84751d40be1bc.1772208939.git.Ankit.Soni@amd.com>
Hi Ankit,
kernel test robot noticed the following build warnings:
[auto build test WARNING on linus/master]
[also build test WARNING on v7.0-rc1 next-20260227]
[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/Ankit-Soni/iommu-amd-Adhere-to-IVINFO-VASIZE-for-address-limits/20260228-010009
base: linus/master
patch link: https://lore.kernel.org/r/cf1a1e3d96c3571ac5caa528caa84751d40be1bc.1772208939.git.Ankit.Soni%40amd.com
patch subject: [PATCH] iommu/amd: Adhere to IVINFO[VASIZE] for address limits
config: x86_64-rhel-9.4-rust (https://download.01.org/0day-ci/archive/20260228/202602281837.QQl5six6-lkp@intel.com/config)
compiler: clang version 20.1.8 (https://github.com/llvm/llvm-project 87f0227cb60147a26a1eeb4fb06e3b505e9c7261)
rustc: rustc 1.88.0 (6b00bc388 2025-06-23)
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20260228/202602281837.QQl5six6-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/202602281837.QQl5six6-lkp@intel.com/
All warnings (new ones prefixed by >>, old ones prefixed by <<):
>> WARNING: modpost: vmlinux: section mismatch in reference: ivinfo_vasize_bits+0x8 (section: .text) -> amd_iommu_disabled (section: .init.data)
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next prev parent reply other threads:[~2026-02-28 10:57 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-27 16:58 Ankit Soni
2026-02-28 10:56 ` kernel test robot [this message]
2026-03-02 23:57 ` Jason Gunthorpe
2026-03-03 11:47 ` Ankit Soni
2026-03-03 12:05 ` Jason Gunthorpe
2026-03-03 17:11 ` Ankit Soni
2026-03-03 18:17 ` Jason Gunthorpe
2026-03-05 13:51 ` Ankit Soni
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=202602281837.QQl5six6-lkp@intel.com \
--to=lkp@intel.com \
--cc=Ankit.Soni@amd.com \
--cc=iommu@lists.linux.dev \
--cc=joro@8bytes.org \
--cc=linux-kernel@vger.kernel.org \
--cc=llvm@lists.linux.dev \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=robin.murphy@arm.com \
--cc=suravee.suthikulpanit@amd.com \
--cc=vasant.hegde@amd.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
all inboxes | Powered by JetHome®