From: Mauro Carvalho Chehab <mchehab+huawei@kernel.org>
To: Jonathan Corbet <corbet@lwn.net>
Cc: linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org,
Akira Yokosawa <akiyks@gmail.com>
Subject: Re: [PATCH 3/9] docs: kdoc: separate out the handling of the declaration phase
Date: Sun, 22 Jun 2025 13:48:57 +0200 [thread overview]
Message-ID: <20250622134857.543cb85a@foz.lan> (raw)
In-Reply-To: <20250621203512.223189-4-corbet@lwn.net>
Em Sat, 21 Jun 2025 14:35:06 -0600
Jonathan Corbet <corbet@lwn.net> escreveu:
> The BODY_MAYBE state really describes the "we are in a declaration" state.
> Rename it accordingly, and split the handling of this state out from that
> of the other BODY* states. This change introduces a fair amount of
> duplicated code that will be coalesced in a later patch.
>
> Signed-off-by: Jonathan Corbet <corbet@lwn.net>
LGTM.
Reviewed-by: Mauro Carvalho Chehab <mchehab+huawei@kernel.org>
> ---
> scripts/lib/kdoc/kdoc_parser.py | 93 +++++++++++++++++++++++++++------
> 1 file changed, 78 insertions(+), 15 deletions(-)
>
> diff --git a/scripts/lib/kdoc/kdoc_parser.py b/scripts/lib/kdoc/kdoc_parser.py
> index d29a61a06f6d..f1491f8c88e7 100644
> --- a/scripts/lib/kdoc/kdoc_parser.py
> +++ b/scripts/lib/kdoc/kdoc_parser.py
> @@ -86,7 +86,7 @@ class state:
> # Parser states
> NORMAL = 0 # normal code
> NAME = 1 # looking for function name
> - BODY_MAYBE = 2 # body - or maybe more description
> + DECLARATION = 2 # We have seen a declaration which might not be done
A way better now.
> BODY = 3 # the body of the comment
> BODY_WITH_BLANK_LINE = 4 # the body which has a blank line
> PROTO = 5 # scanning prototype
> @@ -96,7 +96,7 @@ class state:
> name = [
> "NORMAL",
> "NAME",
> - "BODY_MAYBE",
> + "DECLARATION",
> "BODY",
> "BODY_WITH_BLANK_LINE",
> "PROTO",
> @@ -1287,7 +1287,7 @@ class KernelDoc:
> r = KernRe("[-:](.*)")
> if r.search(line):
> self.entry.declaration_purpose = trim_whitespace(r.group(1))
> - self.state = state.BODY_MAYBE
> + self.state = state.DECLARATION
> else:
> self.entry.declaration_purpose = ""
>
> @@ -1310,9 +1310,82 @@ class KernelDoc:
> else:
> self.emit_msg(ln, f"Cannot find identifier on line:\n{line}")
>
> + def process_decl(self, ln, line):
> + """
> + STATE_DECLARATION: We've seen the beginning of a declaration
> + """
> + if doc_sect.search(line):
> + self.entry.in_doc_sect = True
> + newsection = doc_sect.group(1)
> +
> + if newsection.lower() in ["description", "context"]:
> + newsection = newsection.title()
> +
> + # Special case: @return is a section, not a param description
> + if newsection.lower() in ["@return", "@returns",
> + "return", "returns"]:
> + newsection = "Return"
> +
> + # Perl kernel-doc has a check here for contents before sections.
> + # the logic there is always false, as in_doc_sect variable is
> + # always true. So, just don't implement Wcontents_before_sections
> +
> + # .title()
> + newcontents = doc_sect.group(2)
> + if not newcontents:
> + newcontents = ""
> +
> + if self.entry.contents.strip("\n"):
> + self.dump_section()
> +
> + self.entry.begin_section(ln, newsection)
> + self.entry.leading_space = None
> +
> + self.entry.contents = newcontents.lstrip()
> + if self.entry.contents:
> + self.entry.contents += "\n"
> +
> + self.state = state.BODY
> + return
> +
> + if doc_end.search(line):
> + self.dump_section()
> +
> + # Look for doc_com + <text> + doc_end:
> + r = KernRe(r'\s*\*\s*[a-zA-Z_0-9:\.]+\*/')
> + if r.match(line):
> + self.emit_msg(ln, f"suspicious ending line: {line}")
> +
> + self.entry.prototype = ""
> + self.entry.new_start_line = ln + 1
> +
> + self.state = state.PROTO
> + return
> +
> + if doc_content.search(line):
> + cont = doc_content.group(1)
> +
> + if cont == "":
> + self.state = state.BODY
> + self.entry.contents += "\n" # needed?
> +
> + else:
> + # Continued declaration purpose
> + self.entry.declaration_purpose = self.entry.declaration_purpose.rstrip()
> + self.entry.declaration_purpose += " " + cont
> +
> + r = KernRe(r"\s+")
> + self.entry.declaration_purpose = r.sub(' ',
> + self.entry.declaration_purpose)
> + return
> +
> + # Unknown line, ignore
> + self.emit_msg(ln, f"bad line: {line}")
> +
> +
> def process_body(self, ln, line):
> """
> - STATE_BODY and STATE_BODY_MAYBE: the bulk of a kerneldoc comment.
> + STATE_BODY: the bulk of a kerneldoc comment.
> """
>
> if self.state == state.BODY_WITH_BLANK_LINE:
> @@ -1385,16 +1458,6 @@ class KernelDoc:
>
> self.entry.contents += "\n"
>
> - elif self.state == state.BODY_MAYBE:
> -
> - # Continued declaration purpose
> - self.entry.declaration_purpose = self.entry.declaration_purpose.rstrip()
> - self.entry.declaration_purpose += " " + cont
> -
> - r = KernRe(r"\s+")
> - self.entry.declaration_purpose = r.sub(' ',
> - self.entry.declaration_purpose)
> -
> else:
> if self.entry.section.startswith('@') or \
> self.entry.section == self.section_context:
> @@ -1687,7 +1750,7 @@ class KernelDoc:
> state.NORMAL: process_normal,
> state.NAME: process_name,
> state.BODY: process_body,
> - state.BODY_MAYBE: process_body,
> + state.DECLARATION: process_decl,
> state.BODY_WITH_BLANK_LINE: process_body,
> state.INLINE: process_inline,
> state.PROTO: process_proto,
Thanks,
Mauro
next prev parent reply other threads:[~2025-06-22 11:49 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-21 20:35 [PATCH 0/9] docs: kdoc: rework the BODY* processing states Jonathan Corbet
2025-06-21 20:35 ` [PATCH 1/9] docs: kdoc: Make body_with_blank_line parsing more flexible Jonathan Corbet
2025-06-22 11:46 ` Mauro Carvalho Chehab
2025-06-21 20:35 ` [PATCH 2/9] docs: kdoc: consolidate the "begin section" logic Jonathan Corbet
2025-06-22 11:47 ` Mauro Carvalho Chehab
2025-06-21 20:35 ` [PATCH 3/9] docs: kdoc: separate out the handling of the declaration phase Jonathan Corbet
2025-06-22 11:48 ` Mauro Carvalho Chehab [this message]
2025-06-21 20:35 ` [PATCH 4/9] docs: kdoc: split out the special-section state Jonathan Corbet
2025-06-22 11:50 ` Mauro Carvalho Chehab
2025-06-21 20:35 ` [PATCH 5/9] docs: kdoc: coalesce the new-section handling Jonathan Corbet
2025-06-22 11:50 ` Mauro Carvalho Chehab
2025-06-21 20:35 ` [PATCH 6/9] docs: kdoc: rework the handling of SPECIAL_SECTION Jonathan Corbet
2025-06-22 11:51 ` Mauro Carvalho Chehab
2025-06-21 20:35 ` [PATCH 7/9] docs: kdoc: coalesce the end-of-comment processing Jonathan Corbet
2025-06-22 11:52 ` Mauro Carvalho Chehab
2025-06-21 20:35 ` [PATCH 8/9] docs: kdoc: Add some comments to process_decl() Jonathan Corbet
2025-06-22 11:53 ` Mauro Carvalho Chehab
2025-06-21 20:35 ` [PATCH 9/9] docs: kdoc: finish disentangling the BODY and SPECIAL_SECTION states Jonathan Corbet
2025-06-22 11:54 ` 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=20250622134857.543cb85a@foz.lan \
--to=mchehab+huawei@kernel.org \
--cc=akiyks@gmail.com \
--cc=corbet@lwn.net \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.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;
as well as URLs for NNTP newsgroup(s).