From: "Knop, Ryszard" <ryszard.knop@intel.com>
To: "linux-doc@vger.kernel.org" <linux-doc@vger.kernel.org>,
"rdunlap@infradead.org" <rdunlap@infradead.org>
Cc: "intel-xe@lists.freedesktop.org" <intel-xe@lists.freedesktop.org>,
"Lin, Shuicheng" <shuicheng.lin@intel.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"jani.nikula@linux.intel.com" <jani.nikula@linux.intel.com>
Subject: Re: [PATCH] scripts/kernel-doc: Suggest possible names for excess descriptions
Date: Wed, 15 Jul 2026 11:18:35 +0000 [thread overview]
Message-ID: <2cd1d670895c0c8242e7cea36ab7e1a5b8a12d3e.camel@intel.com> (raw)
In-Reply-To: <12d74842-c826-46ec-922a-68f5e4042cb6@infradead.org>
On Tue, 2026-07-14 at 14:44 -0700, Randy Dunlap wrote:
> Hi,
>
>
> On 7/14/26 4:12 AM, Ryszard Knop wrote:
> > Since check_sections() now warns if a documentation tag member name is
> > the same as defined in the struct, we can suggest names the checker
> > knows, so that it's more obvious how to deal with the warning.
> >
>
> Seems to work for me.
>
> > Signed-off-by: Ryszard Knop <ryszard.knop@intel.com>
> > ---
> > tools/lib/python/kdoc/kdoc_parser.py | 13 +++++++++++--
> > 1 file changed, 11 insertions(+), 2 deletions(-)
> >
> > diff --git a/tools/lib/python/kdoc/kdoc_parser.py b/tools/lib/python/kdoc/kdoc_parser.py
> > index 2dedda215c22..3f88095eab06 100644
> > --- a/tools/lib/python/kdoc/kdoc_parser.py
> > +++ b/tools/lib/python/kdoc/kdoc_parser.py
> > @@ -558,6 +558,13 @@ class KernelDoc:
> > self.push_parameter(ln, decl_type, param, dtype,
> > arg, declaration_name)
> >
> > + def get_suggestions_hint(self, decl_name, possible_names):
> > + suggestions = set(name for name in possible_names if decl_name in name)
> > + if not suggestions:
> > + return ""
> > +
> > + return f"(did you mean one of: '{"', '".join(suggestions)}')"
> > +
> > def check_sections(self, ln, decl_name, decl_type):
> > """
> > Check for errors inside sections, emitting warnings if not found
> > @@ -566,12 +573,13 @@ class KernelDoc:
> > for section in self.entry.sections:
> > if section not in self.entry.parameterlist and \
> > not known_sections.search(section):
> > + hint = self.get_suggestions_hint(section, self.entry.parameterlist)
> > if decl_type == 'function':
> > dname = f"{decl_type} parameter"
> > else:
> > dname = f"{decl_type} member"
> > self.emit_msg(ln,
> > - f"Excess {dname} '{section}' description in '{decl_name}'")
> > + f"Excess {dname} '{section}' description in '{decl_name}' {hint}")
>
> When 'hint' is empty, this statement and/or the similar one below
> adds a trailing space to each of those lines.
> Can you prevent that? (yeah, it's just a nit)
Sure thing, submitted a v2.
>
> >
> > #
> > # Check that documented parameter names (from doc comments, including
> > @@ -591,12 +599,13 @@ class KernelDoc:
> > if param_name in self.entry.parameterlist:
> > continue
> >
> > + hint = self.get_suggestions_hint(param_name, self.entry.parameterlist)
> > if decl_type == 'function':
> > dname = f"{decl_type} parameter"
> > else:
> > dname = f"{decl_type} member"
> > self.emit_msg(ln,
> > - f"Excess {dname} '{param_name}' description in '{decl_name}'")
> > + f"Excess {dname} '{param_name}' description in '{decl_name}' {hint}")
> >
> > def check_return_section(self, ln, declaration_name, return_type):
> > """
>
> Acked-by: Randy Dunlap <rdunlap@infradead.org>
> Tested-by: Randy Dunlap <rdunlap@infradead.org>
>
> thanks.
A.
Thanks, Ryszard
next prev parent reply other threads:[~2026-07-15 11:18 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-14 11:12 [PATCH] scripts/kernel-doc: Suggest possible names for excess descriptions Ryszard Knop
2026-07-14 21:44 ` Randy Dunlap
2026-07-15 11:18 ` Knop, Ryszard [this message]
2026-07-15 11:17 ` [PATCH v2] " Ryszard Knop
2026-07-15 12:42 ` Mauro Carvalho Chehab
2026-07-15 13:21 ` Knop, Ryszard
2026-07-15 13:52 ` Mauro Carvalho Chehab
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=2cd1d670895c0c8242e7cea36ab7e1a5b8a12d3e.camel@intel.com \
--to=ryszard.knop@intel.com \
--cc=intel-xe@lists.freedesktop.org \
--cc=jani.nikula@linux.intel.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rdunlap@infradead.org \
--cc=shuicheng.lin@intel.com \
/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