* [PATCH] Documentation: userspace-api: iommufd: Fix the struct iommu_hwpt_alloc name
@ 2026-09-05 10:38 Karl Mehltretter
2026-09-05 17:32 ` Randy Dunlap
0 siblings, 1 reply; 2+ messages in thread
From: Karl Mehltretter @ 2026-09-05 10:38 UTC (permalink / raw)
To: Jason Gunthorpe, Kevin Tian
Cc: Karl Mehltretter, Jonathan Corbet, iommu, linux-doc, Shuah Khan,
Randy Dunlap, Nicolin Chen
struct iommufd_hwpt_alloc does not exist; the name is struct
iommu_hwpt_alloc.
Use struct iommu_hwpt_alloc.
Fixes: e2d8fe9148b7 ("Documentation: userspace-api: iommufd: Update HWPT_PAGING and HWPT_NESTED")
Assisted-by: LLM
Signed-off-by: Karl Mehltretter <kmehltretter@gmail.com>
---
Documentation/userspace-api/iommufd.rst | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/Documentation/userspace-api/iommufd.rst b/Documentation/userspace-api/iommufd.rst
index f1c4d21e5c5e..763b23339480 100644
--- a/Documentation/userspace-api/iommufd.rst
+++ b/Documentation/userspace-api/iommufd.rst
@@ -242,7 +242,7 @@ creating the objects and links::
Either a manual IOMMUFD_OBJ_HWPT_PAGING or an IOMMUFD_OBJ_HWPT_NESTED is
created via the same IOMMU_HWPT_ALLOC uAPI. The difference is at the type
- of the object passed in via the @pt_id field of struct iommufd_hwpt_alloc.
+ of the object passed in via the @pt_id field of struct iommu_hwpt_alloc.
5. IOMMUFD_OBJ_VIOMMU can be only manually created via the IOMMU_VIOMMU_ALLOC
uAPI, provided a dev_id (for the device's physical IOMMU to back the vIOMMU)
--
2.53.0
^ permalink raw reply related [flat|nested] 2+ messages in thread
* Re: [PATCH] Documentation: userspace-api: iommufd: Fix the struct iommu_hwpt_alloc name
2026-09-05 10:38 [PATCH] Documentation: userspace-api: iommufd: Fix the struct iommu_hwpt_alloc name Karl Mehltretter
@ 2026-09-05 17:32 ` Randy Dunlap
0 siblings, 0 replies; 2+ messages in thread
From: Randy Dunlap @ 2026-09-05 17:32 UTC (permalink / raw)
To: Karl Mehltretter, Jason Gunthorpe, Kevin Tian
Cc: Jonathan Corbet, iommu, linux-doc, Shuah Khan, Nicolin Chen
On 9/5/26 3:38 AM, Karl Mehltretter wrote:
> struct iommufd_hwpt_alloc does not exist; the name is struct
> iommu_hwpt_alloc.
>
> Use struct iommu_hwpt_alloc.
>
> Fixes: e2d8fe9148b7 ("Documentation: userspace-api: iommufd: Update HWPT_PAGING and HWPT_NESTED")
> Assisted-by: LLM
> Signed-off-by: Karl Mehltretter <kmehltretter@gmail.com>
Acked-by: Randy Dunlap <rdunlap@infradead.org>
thanks.
> ---
> Documentation/userspace-api/iommufd.rst | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/Documentation/userspace-api/iommufd.rst b/Documentation/userspace-api/iommufd.rst
> index f1c4d21e5c5e..763b23339480 100644
> --- a/Documentation/userspace-api/iommufd.rst
> +++ b/Documentation/userspace-api/iommufd.rst
> @@ -242,7 +242,7 @@ creating the objects and links::
>
> Either a manual IOMMUFD_OBJ_HWPT_PAGING or an IOMMUFD_OBJ_HWPT_NESTED is
> created via the same IOMMU_HWPT_ALLOC uAPI. The difference is at the type
> - of the object passed in via the @pt_id field of struct iommufd_hwpt_alloc.
> + of the object passed in via the @pt_id field of struct iommu_hwpt_alloc.
>
> 5. IOMMUFD_OBJ_VIOMMU can be only manually created via the IOMMU_VIOMMU_ALLOC
> uAPI, provided a dev_id (for the device's physical IOMMU to back the vIOMMU)
--
~Randy
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2026-09-05 17:32 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2026-09-05 10:38 [PATCH] Documentation: userspace-api: iommufd: Fix the struct iommu_hwpt_alloc name Karl Mehltretter
2026-09-05 17:32 ` Randy Dunlap
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox