From: Jason Gunthorpe <jgg@nvidia•com>
To: Stephen Rothwell <sfr@canb•auug.org.au>
Cc: Nicolin Chen <nicolinc@nvidia•com>,
Linux Kernel Mailing List <linux-kernel@vger•kernel.org>,
Linux Next Mailing List <linux-next@vger•kernel.org>
Subject: Re: linux-next: build warning after merge of the iommufd tree
Date: Fri, 11 Jul 2025 10:38:57 -0300 [thread overview]
Message-ID: <20250711133857.GA1951027@nvidia.com> (raw)
In-Reply-To: <20250711182501.29b6b9b8@canb.auug.org.au>
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
next prev parent reply other threads:[~2025-07-11 13:39 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-11 8:25 linux-next: build warning after merge of the iommufd tree Stephen Rothwell
2025-07-11 13:38 ` Jason Gunthorpe [this message]
-- strict thread matches above, loose matches on Subject: below --
2025-07-11 8:35 Stephen Rothwell
2025-07-11 14:04 ` Jason Gunthorpe
2025-03-21 8:36 Stephen Rothwell
2025-03-21 11:39 ` Jason Gunthorpe
2025-03-26 2:43 ` Valdis Klētnieks
2025-03-18 10:33 Stephen Rothwell
2025-03-28 6:57 ` Stephen Rothwell
2025-03-28 11:49 ` Bagas Sanjaya
2023-03-31 4:41 Stephen Rothwell
2023-03-31 17:45 ` Jason Gunthorpe
2023-03-31 4:31 Stephen Rothwell
2023-03-31 5:09 ` Nicolin Chen
2023-03-31 17:44 ` Jason Gunthorpe
2022-11-08 5:51 Stephen Rothwell
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=20250711133857.GA1951027@nvidia.com \
--to=jgg@nvidia$(echo .)com \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=nicolinc@nvidia$(echo .)com \
--cc=sfr@canb$(echo .)auug.org.au \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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