From: Jonathan Corbet <corbet@lwn.net>
To: Mauro Carvalho Chehab <mchehab+huawei@kernel.org>,
Kees Cook <kees@kernel.org>,
Mauro Carvalho Chehab <mchehab@kernel.org>
Cc: Mauro Carvalho Chehab <mchehab+huawei@kernel.org>,
linux-doc@vger.kernel.org, linux-hardening@vger.kernel.org,
linux-kernel@vger.kernel.org,
"Gustavo A. R. Silva" <gustavoars@kernel.org>,
Aleksandr Loktionov <aleksandr.loktionov@intel.com>,
Randy Dunlap <rdunlap@infradead.org>,
Shuah Khan <skhan@linuxfoundation.org>,
Vincent Mailhol <mailhol@kernel.org>
Subject: Re: [PATCH v3 00/22] kernel-doc: use a C lexical tokenizer for transforms
Date: Sun, 22 Mar 2026 15:08:12 -0600 [thread overview]
Message-ID: <871phbd137.fsf@trenco.lwn.net> (raw)
In-Reply-To: <cover.1773770483.git.mchehab+huawei@kernel.org>
Mauro Carvalho Chehab <mchehab+huawei@kernel.org> writes:
> Hi Jon,
>
> It follows v3 of the series. I basically addressed there the
> points you mentioned. Besides that, I did a fix at CMatch
> group(0) logic, and opted to create a special token for ";",
> as it simplifies the code a little bit and will likely help to
> simplify future changes.
OK, I have gone ahead and applied this series...it doesn't seem to
explode for me, anyway :) Let's hope for the best...
Thanks,
jon
prev parent reply other threads:[~2026-03-22 21:08 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-17 18:09 [PATCH v3 00/22] kernel-doc: use a C lexical tokenizer for transforms Mauro Carvalho Chehab
2026-03-17 18:09 ` [PATCH v3 01/22] docs: python: add helpers to run unit tests Mauro Carvalho Chehab
2026-03-17 18:09 ` [PATCH v3 02/22] unittests: add a testbench to check public/private kdoc comments Mauro Carvalho Chehab
2026-03-17 18:09 ` [PATCH v3 03/22] docs: kdoc: don't add broken comments inside prototypes Mauro Carvalho Chehab
2026-03-18 7:47 ` Loktionov, Aleksandr
2026-03-17 18:09 ` [PATCH v3 04/22] docs: kdoc: properly handle empty enum arguments Mauro Carvalho Chehab
2026-03-17 18:09 ` [PATCH v3 05/22] docs: add a C tokenizer to be used by kernel-doc Mauro Carvalho Chehab
2026-03-17 18:09 ` [PATCH v3 06/22] docs: kdoc: use tokenizer to handle comments on structs Mauro Carvalho Chehab
2026-03-18 7:48 ` Loktionov, Aleksandr
2026-03-17 18:09 ` [PATCH v3 07/22] unittests: test_private: modify it to use CTokenizer directly Mauro Carvalho Chehab
2026-03-17 18:09 ` [PATCH v3 08/22] unittests: test_tokenizer: check if the tokenizer works Mauro Carvalho Chehab
2026-03-17 18:09 ` [PATCH v3 09/22] unittests: add a runner to execute all unittests Mauro Carvalho Chehab
2026-03-17 18:09 ` [PATCH v3 10/22] docs: kdoc: create a CMatch to match nested C blocks Mauro Carvalho Chehab
2026-03-17 18:09 ` [PATCH v3 11/22] tools: unittests: add tests for CMatch Mauro Carvalho Chehab
2026-03-17 18:09 ` [PATCH v3 12/22] docs: c_lex: properly implement a sub() method " Mauro Carvalho Chehab
2026-03-17 18:09 ` [PATCH v3 13/22] unittests: test_cmatch: add tests for sub() Mauro Carvalho Chehab
2026-03-17 18:09 ` [PATCH v3 14/22] docs: kdoc: replace NestedMatch with CMatch Mauro Carvalho Chehab
2026-03-17 18:09 ` [PATCH v3 15/22] docs: kdoc_re: get rid of NestedMatch class Mauro Carvalho Chehab
2026-03-17 18:09 ` [PATCH v3 16/22] docs: xforms_lists: handle struct_group directly Mauro Carvalho Chehab
2026-03-17 18:09 ` [PATCH v3 17/22] docs: xforms_lists: better evaluate struct_group macros Mauro Carvalho Chehab
2026-03-18 7:44 ` Loktionov, Aleksandr
2026-03-17 18:09 ` [PATCH v3 18/22] docs: c_lex: setup a logger to report tokenizer issues Mauro Carvalho Chehab
2026-03-18 7:45 ` Loktionov, Aleksandr
2026-03-17 18:09 ` [PATCH v3 19/22] docs: kernel-doc.rst: document private: scope propagation Mauro Carvalho Chehab
2026-03-17 18:09 ` [PATCH v3 20/22] docs: kdoc: ensure that comments are dropped before calling split_struct_proto() Mauro Carvalho Chehab
2026-03-17 18:09 ` [PATCH v3 21/22] docs: kdoc_parser: avoid tokenizing structs everytime Mauro Carvalho Chehab
2026-03-17 18:09 ` [PATCH v3 22/22] docs: xforms_lists: use CMatch for all identifiers Mauro Carvalho Chehab
2026-03-22 21:08 ` Jonathan Corbet [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=871phbd137.fsf@trenco.lwn.net \
--to=corbet@lwn.net \
--cc=aleksandr.loktionov@intel.com \
--cc=gustavoars@kernel.org \
--cc=kees@kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-hardening@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mailhol@kernel.org \
--cc=mchehab+huawei@kernel.org \
--cc=mchehab@kernel.org \
--cc=rdunlap@infradead.org \
--cc=skhan@linuxfoundation.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