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 2/9] docs: kdoc: consolidate the "begin section" logic
Date: Sun, 22 Jun 2025 13:47:19 +0200 [thread overview]
Message-ID: <20250622134719.1b9818c7@foz.lan> (raw)
In-Reply-To: <20250621203512.223189-3-corbet@lwn.net>
Em Sat, 21 Jun 2025 14:35:05 -0600
Jonathan Corbet <corbet@lwn.net> escreveu:
> Pull the repeated "begin a section" logic into a single place and hide it
> within the KernelEntry class.
>
> Signed-off-by: Jonathan Corbet <corbet@lwn.net>
Heh, I had a code snippet similar to this one on one of my test branches ;-)
LGTM.
Reviewed-by: Mauro Carvalho Chehab <mchehab+huawei@kernel.org>
> ---
> scripts/lib/kdoc/kdoc_parser.py | 32 +++++++++++++++++---------------
> 1 file changed, 17 insertions(+), 15 deletions(-)
>
> diff --git a/scripts/lib/kdoc/kdoc_parser.py b/scripts/lib/kdoc/kdoc_parser.py
> index c46e1b6a7d4b..d29a61a06f6d 100644
> --- a/scripts/lib/kdoc/kdoc_parser.py
> +++ b/scripts/lib/kdoc/kdoc_parser.py
> @@ -169,6 +169,15 @@ class KernelEntry:
> self.warnings.append(log_msg)
> return
>
> + #
> + # Begin a new section.
> + #
> + def begin_section(self, line_no, title = SECTION_DEFAULT, dump = False):
> + if dump:
> + self.dump_section(start_new = True)
> + self.section = title
> + self.new_start_line = line_no
> +
> def dump_section(self, start_new=True):
> """
> Dumps section contents to arrays/hashes intended for that purpose.
> @@ -1231,12 +1240,11 @@ class KernelDoc:
> # Check for a DOC: block and handle them specially.
> #
> if doc_block.search(line):
> - self.entry.new_start_line = ln
>
> if not doc_block.group(1):
> - self.entry.section = "Introduction"
> + self.entry.begin_section(ln, "Introduction")
> else:
> - self.entry.section = doc_block.group(1)
> + self.entry.begin_section(ln, doc_block.group(1))
>
> self.entry.identifier = self.entry.section
> self.state = state.DOCBLOCK
> @@ -1270,8 +1278,7 @@ class KernelDoc:
> self.state = state.BODY
> self.entry.identifier = self.entry.identifier.strip(" ")
> # if there's no @param blocks need to set up default section here
> - self.entry.section = SECTION_DEFAULT
> - self.entry.new_start_line = ln + 1
> + self.entry.begin_section(ln + 1)
> #
> # Find the description portion, which *should* be there but
> # isn't always.
> @@ -1312,8 +1319,7 @@ class KernelDoc:
> r = KernRe(r"\s*\*\s*\S")
> if r.match(line):
> self.dump_section()
> - self.entry.section = SECTION_DEFAULT
> - self.entry.new_start_line = ln
> + self.entry.begin_section(ln)
> self.entry.contents = ""
>
> if doc_sect.search(line):
> @@ -1340,8 +1346,7 @@ class KernelDoc:
> if self.entry.contents.strip("\n"):
> self.dump_section()
>
> - self.entry.new_start_line = ln
> - self.entry.section = newsection
> + self.entry.begin_section(ln, newsection)
> self.entry.leading_space = None
>
> self.entry.contents = newcontents.lstrip()
> @@ -1370,9 +1375,7 @@ class KernelDoc:
>
> if cont == "":
> if self.entry.section == self.section_context:
> - self.dump_section()
> -
> - self.entry.new_start_line = ln
> + self.entry.begin_section(ln, dump = True)
> self.state = state.BODY
> else:
> if self.entry.section != SECTION_DEFAULT:
> @@ -1427,8 +1430,7 @@ class KernelDoc:
>
> if self.inline_doc_state == state.INLINE_NAME and \
> doc_inline_sect.search(line):
> - self.entry.section = doc_inline_sect.group(1)
> - self.entry.new_start_line = ln
> + self.entry.begin_section(ln, doc_inline_sect.group(1))
>
> self.entry.contents = doc_inline_sect.group(2).lstrip()
> if self.entry.contents != "":
> @@ -1627,7 +1629,7 @@ class KernelDoc:
> """STATE_PROTO: reading a function/whatever prototype."""
>
> if doc_inline_oneline.search(line):
> - self.entry.section = doc_inline_oneline.group(1)
> + self.entry.begin_section(ln, doc_inline_oneline.group(1))
> self.entry.contents = doc_inline_oneline.group(2)
>
> if self.entry.contents != "":
Thanks,
Mauro
next prev parent reply other threads:[~2025-06-22 11:47 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 [this message]
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
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=20250622134719.1b9818c7@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
all inboxes | Powered by JetHome®