All of lore.kernel.org
 help / color / mirror / Atom feed
From: Nicolin Chen <nicolinc@nvidia.com>
To: Bagas Sanjaya <bagasdotme@gmail.com>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	"Linux Documentation" <linux-doc@vger.kernel.org>,
	Linux IOMMU <iommu@lists.linux.dev>,
	Jason Gunthorpe <jgg@ziepe.ca>, Kevin Tian <kevin.tian@intel.com>,
	Pranjal Shrivastava <praan@google.com>,
	"Stephen Rothwell" <sfr@canb.auug.org.au>
Subject: Re: [PATCH] iommu/arm-smmu-v3-iommufd: Separate vDEVICE allocation list
Date: Tue, 25 Nov 2025 19:58:50 -0800	[thread overview]
Message-ID: <aSZ6+mY45RCXoKP0@Asurada-Nvidia> (raw)
In-Reply-To: <20251126033602.28871-2-bagasdotme@gmail.com>

On Wed, Nov 26, 2025 at 10:36:03AM +0700, Bagas Sanjaya wrote:
> Stephen Rothwell reports htmldocs warnings when merging iommufd tree:
> 
> Documentation/userspace-api/iommufd:335: include/uapi/linux/iommufd.h:456: ERROR: Unexpected indentation. [docutils]
> Documentation/userspace-api/iommufd:335: include/uapi/linux/iommufd.h:457: WARNING: Block quote ends without a blank line; unexpected unindent. [docutils]
> 
> Fix them by separating vDEVICE allocation list from preceding paragraph.
> 
> Fixes: 9f0b286fe40130 ("iommu/arm-smmu-v3-iommufd: Allow attaching nested domain for GBPA cases")
> Reported-by: Stephen Rothwell <sfr@canb.auug.org.au>
> Closes: https://lore.kernel.org/linux-next/20251126125920.207fc959@canb.auug.org.au/
> Signed-off-by: Bagas Sanjaya <bagasdotme@gmail.com>

Thanks for the fix.

I was about to send a v3 over a fix :)

Anyway,

Acked-by: Nicolin Chen <nicolinc@nvidia.com>

  reply	other threads:[~2025-11-26  3:59 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-11-26  3:36 [PATCH] iommu/arm-smmu-v3-iommufd: Separate vDEVICE allocation list Bagas Sanjaya
2025-11-26  3:58 ` Nicolin Chen [this message]
2025-11-26 18:22 ` Jason Gunthorpe

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=aSZ6+mY45RCXoKP0@Asurada-Nvidia \
    --to=nicolinc@nvidia.com \
    --cc=bagasdotme@gmail.com \
    --cc=iommu@lists.linux.dev \
    --cc=jgg@ziepe.ca \
    --cc=kevin.tian@intel.com \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=praan@google.com \
    --cc=sfr@canb.auug.org.au \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.