From: Bagas Sanjaya <bagasdotme@gmail•com>
To: Stephen Rothwell <sfr@canb•auug.org.au>,
Jason Gunthorpe <jgg@nvidia•com>
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, 28 Mar 2025 18:49:06 +0700 [thread overview]
Message-ID: <Z-aMsk148w8zgaRQ@archie.me> (raw)
In-Reply-To: <20250328175745.7ecfee87@canb.auug.org.au>
[-- Attachment #1: Type: text/plain, Size: 1183 bytes --]
On Fri, Mar 28, 2025 at 05:57:45PM +1100, Stephen Rothwell wrote:
> Hi all,
>
> On Tue, 18 Mar 2025 21:33:59 +1100 Stephen Rothwell <sfr@canb•auug.org.au> wrote:
> >
> > After merging the iommufd tree, today's linux-next build (htmldocs)
> > produced this warning:
> >
> > Documentation/userspace-api/iommufd:323: include/uapi/linux/iommufd.h:1033: CRITICAL: Unexpected section title or transition.
> >
> > ------------------------------------------------------------------------- [docutils]
> > WARNING: kernel-doc 'scripts/kernel-doc -rst -enable-lineno include/uapi/linux/iommufd.h' processing failed with: Documentation/userspace-api/iommufd:323: include/uapi/linux/iommufd.h:1033: (SEVERE/4) Unexpected section title or transition.
> >
> > -------------------------------------------------------------------------
> >
> > Introduced by commit
> >
> > 50c842dd6cd3 ("iommufd: Add IOMMUFD_OBJ_VEVENTQ and IOMMUFD_CMD_VEVENTQ_ALLOC")
>
> Any progress on this?
Should've been fixed by [1].
Thanks.
[1]: https://lore.kernel.org/linux-doc/20250328114654.55840-1-bagasdotme@gmail.com/
--
An old man doll... just what I always wanted! - Clara
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
next prev parent reply other threads:[~2025-03-28 11:49 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-18 10:33 linux-next: build warning after merge of the iommufd tree Stephen Rothwell
2025-03-28 6:57 ` Stephen Rothwell
2025-03-28 11:49 ` Bagas Sanjaya [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-07-11 8:25 Stephen Rothwell
2025-07-11 13:38 ` Jason Gunthorpe
2025-03-21 8:36 Stephen Rothwell
2025-03-21 11:39 ` Jason Gunthorpe
2025-03-26 2:43 ` Valdis Klētnieks
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=Z-aMsk148w8zgaRQ@archie.me \
--to=bagasdotme@gmail$(echo .)com \
--cc=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