linux-kernel - Re: linux-next: build warning after merge of the iommufd tree

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <20250711133857.GA1951027@nvidia.com>
Date: Fri, 11 Jul 2025 10:38:57 -0300
From: Jason Gunthorpe <jgg@...dia.com>
To: Stephen Rothwell <sfr@...b.auug.org.au>
Cc: Nicolin Chen <nicolinc@...dia.com>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	Linux Next Mailing List <linux-next@...r.kernel.org>
Subject: Re: linux-next: build warning after merge of the iommufd tree

On Fri, Jul 11, 2025 at 06:25:01PM +1000, Stephen Rothwell wrote:
> Hi all,
> 
> After merging the iommufd tree, today's linux-next build (htmldocs)
> produced this warning:
> 
> Documentation/userspace-api/iommufd:335: include/uapi/linux/iommufd.h:1272: ERROR: Unexpected indentation. [docutils]
> 
> Introduced by commit
> 
>   c4e9e9b4227e ("iommufd/viommu: Add IOMMUFD_CMD_HW_QUEUE_ALLOC ioctl")

I fixed this with:

--- a/include/uapi/linux/iommufd.h
+++ b/include/uapi/linux/iommufd.h
@@ -1175,7 +1175,8 @@ enum iommu_hw_queue_type {
  * and @length.
  *
  * A vIOMMU can allocate multiple queues, but it must use a different @index per
- * type to separate each allocation, e.g.
+ * type to separate each allocation, e.g::
+ *
  *     Type1 HW queue0, Type1 HW queue1, Type2 HW queue0, ...
  */
 struct iommu_hw_queue_alloc {

Thanks,
Jason