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 0/8] Yet another set of kerneldoc simplifications
Date: Sat, 28 Jun 2025 16:22:09 +0200 [thread overview]
Message-ID: <20250628162209.0ba297b5@foz.lan> (raw)
In-Reply-To: <20250627184000.132291-1-corbet@lwn.net>
Em Fri, 27 Jun 2025 12:39:52 -0600
Jonathan Corbet <corbet@lwn.net> escreveu:
> As I continue to work through our shiny new kerneldoc, I keep finding ways
> to make it (IMO) shinier. This set covers these basic areas:
>
> - Remove some unused fields from the KernelEntry class, and encapsulate the
> handling of the section contentions therein.
>
> - Clean up and optimize the EXPORT_SYMBOL processing slightly.
>
> - Rework the handling of inline comments by getting rid of the substate
> design and separating out the processing of the states that remain.
>
> The series results in no changes in the generated output.
I looked the entire series, although I didn't test. On a visual
inspection, all changes look good to me.
Reviewed-by: Mauro Carvalho Chehab <mchehab+huawei@kernel.org>
>
> Jonathan Corbet (8):
> docs: kdoc: remove KernelEntry::in_doc_sect
> docs: kdoc: Move content handling into KernelEntry
> docs: kdoc: remove a bit of dead code
> docs: kdoc: remove KernelEntry::function
> docs: kdoc: rework process_export() slightly
> docs: kdoc: remove the INLINE_END state
> docs: kdoc: remove the inline states-within-a-state
> docs: kdoc: split the processing of the two remaining inline states
>
> scripts/lib/kdoc/kdoc_parser.py | 170 +++++++++++++-------------------
> 1 file changed, 67 insertions(+), 103 deletions(-)
>
Thanks,
Mauro
prev parent reply other threads:[~2025-06-28 14:22 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-27 18:39 [PATCH 0/8] Yet another set of kerneldoc simplifications Jonathan Corbet
2025-06-27 18:39 ` [PATCH 1/8] docs: kdoc: remove KernelEntry::in_doc_sect Jonathan Corbet
2025-06-27 18:39 ` [PATCH 2/8] docs: kdoc: Move content handling into KernelEntry Jonathan Corbet
2025-06-27 18:39 ` [PATCH 3/8] docs: kdoc: remove a bit of dead code Jonathan Corbet
2025-06-27 18:39 ` [PATCH 4/8] docs: kdoc: remove KernelEntry::function Jonathan Corbet
2025-06-27 18:39 ` [PATCH 5/8] docs: kdoc: rework process_export() slightly Jonathan Corbet
2025-06-27 18:39 ` [PATCH 6/8] docs: kdoc: remove the INLINE_END state Jonathan Corbet
2025-06-27 18:39 ` [PATCH 7/8] docs: kdoc: remove the inline states-within-a-state Jonathan Corbet
2025-06-27 18:40 ` [PATCH 8/8] docs: kdoc: split the processing of the two remaining inline states Jonathan Corbet
2025-06-28 14:22 ` Mauro Carvalho Chehab [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=20250628162209.0ba297b5@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