From: Jason Gunthorpe <jgg@ziepe.ca>
To: Randy Dunlap <rdunlap@infradead.org>
Cc: linux-kernel@vger.kernel.org,
Andrew Morton <akpm@linux-foundation.org>,
linux-mm@kvack.org
Subject: Re: [PATCH] mm/mmu_notifier: clean up mmu_notifier.h kernel-doc
Date: Mon, 2 Mar 2026 10:25:21 -0400 [thread overview]
Message-ID: <20260302142521.GX44359@ziepe.ca> (raw)
In-Reply-To: <20260302005222.3470783-1-rdunlap@infradead.org>
On Sun, Mar 01, 2026 at 04:52:22PM -0800, Randy Dunlap wrote:
> Eliminate kernel-doc warnings in mmu_notifier.h:
> - add a missing struct short description
> - use the correct format for function parameters
> - add missing function return comment sections
>
> Warning: include/linux/mmu_notifier.h:236 missing initial short
> description on line: * struct mmu_interval_notifier_ops
> Warning: include/linux/mmu_notifier.h:325 function parameter 'interval_sub'
> not described in 'mmu_interval_set_seq'
> Warning: include/linux/mmu_notifier.h:325 function parameter 'cur_seq'
> not described in 'mmu_interval_set_seq'
> Warning: include/linux/mmu_notifier.h:346 function parameter 'interval_sub'
> not described in 'mmu_interval_read_retry'
> Warning: include/linux/mmu_notifier.h:346 function parameter 'seq' not
> described in 'mmu_interval_read_retry'
> Warning: include/linux/mmu_notifier.h:346 No description found for return
> value of 'mmu_interval_read_retry'
> Warning: include/linux/mmu_notifier.h:370 function parameter 'interval_sub'
> not described in 'mmu_interval_check_retry'
> Warning: include/linux/mmu_notifier.h:370 function parameter 'seq' not
> described in 'mmu_interval_check_retry'
> Warning: include/linux/mmu_notifier.h:370 No description found for return
> value of 'mmu_interval_check_retry'
>
> Signed-off-by: Randy Dunlap <rdunlap@infradead.org>
> ---
> Cc: Jason Gunthorpe <jgg@ziepe.ca>
> Cc: Andrew Morton <akpm@linux-foundation.org>
> Cc: linux-mm@kvack.org
>
> include/linux/mmu_notifier.h | 31 ++++++++++++++++---------------
> 1 file changed, 16 insertions(+), 15 deletions(-)
Reviewed-by: Jason Gunthorpe <jgg@nvidia.com>
Jason
prev parent reply other threads:[~2026-03-02 14:25 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-02 0:52 Randy Dunlap
2026-03-02 14:25 ` Jason Gunthorpe [this message]
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=20260302142521.GX44359@ziepe.ca \
--to=jgg@ziepe.ca \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=rdunlap@infradead.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