From: Nicolin Chen <nicolinc@nvidia.com>
To: <jgg@nvidia.com>, <kevin.tian@intel.com>
Cc: <robin.murphy@arm.com>, <joro@8bytes.org>, <will@kernel.org>,
<iommu@lists.linux.dev>, <linux-kernel@vger.kernel.org>,
<shuah@kernel.org>, <linux-kselftest@vger.kernel.org>,
<shyamsaini@linux.microsoft.com>
Subject: Re: [PATCH v2 4/7] iommufd: Add IOMMU_OPTION_SW_MSI_START/SIZE ioctls
Date: Wed, 15 Oct 2025 10:20:28 -0700 [thread overview]
Message-ID: <aO/X3EwzRLOj0IL1@Asurada-Nvidia> (raw)
In-Reply-To: <6c36de14b00a3f06df3a602f18baf6b51fde429f.1760487869.git.nicolinc@nvidia.com>
On Tue, Oct 14, 2025 at 05:29:36PM -0700, Nicolin Chen wrote:
> @@ -1458,18 +1458,27 @@ int iopt_table_enforce_dev_resv_regions(struct io_pagetable *iopt,
> iommu_get_resv_regions(dev, &resv_regions);
>
> list_for_each_entry(resv, &resv_regions, list) {
> + unsigned long start = PHYS_ADDR_MAX, last = 0;
kernel test robot complained. It should be:
phys_addr_t start = PHYS_ADDR_MAX, last = 0;
Will fix in next version.
Thanks
Nicolin
next prev parent reply other threads:[~2025-10-15 17:20 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-15 0:29 [PATCH v2 0/7] iommufd: Add MSI mapping support with nested SMMU (Part-2 RMR) Nicolin Chen
2025-10-15 0:29 ` [PATCH v2 1/7] iommufd/device: Move sw_msi_start from igroup to idev Nicolin Chen
2025-10-15 0:29 ` [PATCH v2 2/7] iommufd: Pass in idev to iopt_table_enforce_dev_resv_regions Nicolin Chen
2025-10-15 0:29 ` [PATCH v2 3/7] iommufd/device: Make iommufd_device_is_attached non-static Nicolin Chen
2025-10-15 0:29 ` [PATCH v2 4/7] iommufd: Add IOMMU_OPTION_SW_MSI_START/SIZE ioctls Nicolin Chen
2025-10-15 11:58 ` kernel test robot
2025-10-15 17:20 ` Nicolin Chen [this message]
2025-10-15 0:29 ` [PATCH v2 5/7] iommufd/selftest: Add MOCK_FLAGS_DEVICE_NO_ATTACH Nicolin Chen
2025-10-15 0:29 ` [PATCH v2 6/7] iommufd/selftest: Add a testing reserved region Nicolin Chen
2025-10-15 0:29 ` [PATCH v2 7/7] iommufd/selftest: Add coverage for IOMMU_OPTION_SW_MSI_START/SIZE Nicolin Chen
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=aO/X3EwzRLOj0IL1@Asurada-Nvidia \
--to=nicolinc@nvidia.com \
--cc=iommu@lists.linux.dev \
--cc=jgg@nvidia.com \
--cc=joro@8bytes.org \
--cc=kevin.tian@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=robin.murphy@arm.com \
--cc=shuah@kernel.org \
--cc=shyamsaini@linux.microsoft.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).