From: Jason Gunthorpe <jgg@ziepe.ca>
To: Randy Dunlap <rdunlap@infradead.org>
Cc: linux-kernel@vger.kernel.org, Joerg Roedel <joro@8bytes.org>,
Will Deacon <will@kernel.org>,
Robin Murphy <robin.murphy@arm.com>,
iommu@lists.linux.dev
Subject: Re: [PATCH] iommu/io-pgtable: fix all kernel-doc warnings in io-pgtable.h
Date: Mon, 2 Mar 2026 19:58:23 -0400 [thread overview]
Message-ID: <20260302235823.GZ44359@ziepe.ca> (raw)
In-Reply-To: <20260302005214.3469521-1-rdunlap@infradead.org>
On Sun, Mar 01, 2026 at 04:52:14PM -0800, Randy Dunlap wrote:
> Avoid kernel-doc warnings in io-pgtable.h:
> - use the correct struct member names or kernel-doc format
> - add a missing struct member description
> - add a missing function return comment section
>
> Warning: include/linux/io-pgtable.h:187 struct member 'coherent_walk' not
> described in 'io_pgtable_cfg'
> Warning: include/linux/io-pgtable.h:187 struct member 'arm_lpae_s1_cfg' not
> described in 'io_pgtable_cfg'
> Warning: include/linux/io-pgtable.h:187 struct member 'arm_lpae_s2_cfg' not
> described in 'io_pgtable_cfg'
> Warning: include/linux/io-pgtable.h:187 struct member 'arm_v7s_cfg' not
> described in 'io_pgtable_cfg'
> Warning: include/linux/io-pgtable.h:187 struct member 'arm_mali_lpae_cfg'
> not described in 'io_pgtable_cfg'
> Warning: include/linux/io-pgtable.h:187 struct member 'apple_dart_cfg' not
> described in 'io_pgtable_cfg'
> Warning: include/linux/io-pgtable.h:187 struct member 'amd' not described
> in 'io_pgtable_cfg'
> Warning: include/linux/io-pgtable.h:223 struct member
> 'read_and_clear_dirty' not described in 'io_pgtable_ops'
> Warning: include/linux/io-pgtable.h:237 No description found for return
> value of 'alloc_io_pgtable_ops'
>
> Signed-off-by: Randy Dunlap <rdunlap@infradead.org>
> ---
> Cc: Joerg Roedel <joro@8bytes.org>
> Cc: Will Deacon <will@kernel.org>
> Cc: Robin Murphy <robin.murphy@arm.com>
> Cc: iommu@lists.linux.dev
>
> include/linux/io-pgtable.h | 10 ++++++++--
> 1 file changed, 8 insertions(+), 2 deletions(-)
Reviewed-by: Jason Gunthorpe <jgg@nvidia.com>
Jason
next prev parent reply other threads:[~2026-03-02 23:58 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-02 0:52 [PATCH] iommu/io-pgtable: fix all kernel-doc warnings in io-pgtable.h Randy Dunlap
2026-03-02 23:58 ` Jason Gunthorpe [this message]
2026-03-17 12:59 ` Joerg Roedel
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=20260302235823.GZ44359@ziepe.ca \
--to=jgg@ziepe.ca \
--cc=iommu@lists.linux.dev \
--cc=joro@8bytes.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rdunlap@infradead.org \
--cc=robin.murphy@arm.com \
--cc=will@kernel.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