Linux Documentation
 help / color / mirror / Atom feed
From: Jonathan Corbet <corbet@lwn.net>
To: Karl Mehltretter <kmehltretter@gmail.com>,
	Jason Gunthorpe <jgg@ziepe.ca>, Kevin Tian <kevin.tian@intel.com>
Cc: Karl Mehltretter <kmehltretter@gmail.com>,
	iommu@lists.linux.dev, linux-doc@vger.kernel.org,
	Shuah Khan <skhan@linuxfoundation.org>,
	Randy Dunlap <rdunlap@infradead.org>,
	Nicolin Chen <nicolinc@nvidia.com>
Subject: Re: [PATCH] Documentation: userspace-api: iommufd: Fix the struct iommu_hwpt_alloc name
Date: Mon, 07 Sep 2026 09:43:42 -0600	[thread overview]
Message-ID: <8733vlxe1d.fsf@trenco.lwn.net> (raw)
In-Reply-To: <20260905103819.43424-1-kmehltretter@gmail.com>

Karl Mehltretter <kmehltretter@gmail.com> writes:

> 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.

Applied, thanks.

jon

      parent reply	other threads:[~2026-09-07 15:43 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
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
2026-09-07 15:43 ` Jonathan Corbet [this message]

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=8733vlxe1d.fsf@trenco.lwn.net \
    --to=corbet@lwn.net \
    --cc=iommu@lists.linux.dev \
    --cc=jgg@ziepe.ca \
    --cc=kevin.tian@intel.com \
    --cc=kmehltretter@gmail.com \
    --cc=linux-doc@vger.kernel.org \
    --cc=nicolinc@nvidia.com \
    --cc=rdunlap@infradead.org \
    --cc=skhan@linuxfoundation.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