From: Herbert Xu <herbert@gondor.apana.org.au>
To: Randy Dunlap <rdunlap@infradead.org>
Cc: linux-kernel@vger.kernel.org, Thomas Graf <tgraf@suug.ch>,
linux-crypto@vger.kernel.org
Subject: Re: [PATCH] rhashtable: headers: add missing members, remove excess ones
Date: Fri, 13 Nov 2026 21:05:08 +0800 [thread overview]
Message-ID: <avcLBErMDphzdfed@gondor.apana.org.au> (raw)
In-Reply-To: <20261103031547.2662864-1-rdunlap@infradead.org>
On Mon, Nov 02, 2026 at 07:15:47PM -0800, Randy Dunlap wrote:
> Add or remove kernel-doc comments for missing or excess struct members
> and function (or macro) parameters to prevent these kernel-doc warnings:
>
> Warning: include/linux/rhashtable-types.h:108 struct member 'alloc_tag' not described in 'rhashtable'
> Warning: include/linux/rhashtable-types.h:108 struct member 'lockdep_key' not described in 'rhashtable'
> Warning: include/linux/rhashtable-types.h:145 struct member 'end_of_table' not described in 'rhashtable_iter'
> Warning: include/linux/rhashtable-types.h:199 Excess function parameter 'ht' description in 'rhashtable_init'
> Warning: include/linux/rhashtable-types.h:199 Excess function parameter 'params' description in 'rhashtable_init'
> Warning: include/linux/rhashtable-types.h:220 Excess function parameter 'hlt' description in 'rhltable_init'
> Warning: include/linux/rhashtable-types.h:220 Excess function parameter 'params' description in 'rhltable_init'
>
> Warning: include/linux/rhashtable.h:87 struct member 'dep_map' not described in 'bucket_table'
> Warning: include/linux/rhashtable.h:87 Excess struct member 'rehash' description in 'bucket_table'
> Warning: include/linux/rhashtable.h:87 Excess struct member 'ntbl' description in 'bucket_table'
>
> Signed-off-by: Randy Dunlap <rdunlap@infradead.org>
> ---
> Cc: Thomas Graf <tgraf@suug.ch>
> Cc: Herbert Xu <herbert@gondor.apana.org.au>
> Cc: linux-crypto@vger.kernel.org
>
> include/linux/rhashtable-types.h | 11 +++++++----
> include/linux/rhashtable.h | 3 +--
> 2 files changed, 8 insertions(+), 6 deletions(-)
Patch applied. Thanks.
--
Email: Herbert Xu <herbert@gondor.apana.org.au>
Home Page: http://gondor.apana.org.au/~herbert/
PGP Key: http://gondor.apana.org.au/~herbert/pubkey.txt
prev parent reply other threads:[~2026-11-13 13:05 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-03 3:15 [PATCH] rhashtable: headers: add missing members, remove excess ones Randy Dunlap
2026-11-13 13:05 ` Herbert Xu [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=avcLBErMDphzdfed@gondor.apana.org.au \
--to=herbert@gondor.apana.org.au \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rdunlap@infradead.org \
--cc=tgraf@suug.ch \
/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