From: Akira Yokosawa <akiyks@gmail.com>
To: Jonathan Corbet <corbet@lwn.net>, linux-doc@vger.kernel.org
Cc: linux-kernel@vger.kernel.org,
Mauro Carvalho Chehab <mchehab+huawei@kernel.org>,
Akira Yokosawa <akiyks@gmail.com>
Subject: Re: [PATCH 0/7] Further kernel-doc tweakery
Date: Fri, 4 Jul 2025 00:01:02 +0900 [thread overview]
Message-ID: <e675d05d-0d81-47cc-b431-641b5b8c57b8@gmail.com> (raw)
In-Reply-To: <20250701205730.146687-1-corbet@lwn.net>
Hi Jon,
On Tue, 1 Jul 2025 14:57:23 -0600, Jonathan Corbet wrote:
> This is a set of miscellaneous improvements, finishing my pass over the
> first parsing pass and getting into the second ("dump_*") pass.
>
> Jonathan Corbet (7):
> docs: kdoc: don't reinvent string.strip()
> docs: kdoc: micro-optimize KernRe
> docs: kdoc: remove the brcount floor in process_proto_type()
> docs: kdoc: rework type prototype parsing
> docs: kdoc: some tweaks to process_proto_function()
> docs: kdoc: Remove a Python 2 comment
> docs: kdoc: pretty up dump_enum()
>
> Documentation/sphinx/kerneldoc.py | 2 -
> scripts/lib/kdoc/kdoc_parser.py | 150 +++++++++++++++---------------
> scripts/lib/kdoc/kdoc_re.py | 6 +-
> 3 files changed, 79 insertions(+), 79 deletions(-)
>
I just applied this set and got the error of:
---------------------------------------------------------------
File "/<srcdir>/scripts/lib/kdoc/kdoc_parser.py", line 881
else:
^
TabError: inconsistent use of tabs and spaces in indentation
---------------------------------------------------------------
I didn't look into individual patches, assuming it should be an easy fix
for you.
I guess it'd be better to test (and hopefully to review) other pending
series from you and Mauro ...
Thanks, Akira
next prev parent reply other threads:[~2025-07-03 15:01 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-01 20:57 [PATCH 0/7] Further kernel-doc tweakery Jonathan Corbet
2025-07-01 20:57 ` [PATCH 1/7] docs: kdoc: don't reinvent string.strip() Jonathan Corbet
2025-07-03 15:43 ` Mauro Carvalho Chehab
2025-07-01 20:57 ` [PATCH 2/7] docs: kdoc: micro-optimize KernRe Jonathan Corbet
2025-07-03 15:38 ` Mauro Carvalho Chehab
2025-07-03 18:14 ` Jonathan Corbet
2025-07-03 22:27 ` Mauro Carvalho Chehab
2025-07-01 20:57 ` [PATCH 3/7] docs: kdoc: remove the brcount floor in process_proto_type() Jonathan Corbet
2025-07-03 15:39 ` Mauro Carvalho Chehab
2025-07-01 20:57 ` [PATCH 4/7] docs: kdoc: rework type prototype parsing Jonathan Corbet
2025-07-03 15:46 ` Mauro Carvalho Chehab
2025-07-01 20:57 ` [PATCH 5/7] docs: kdoc: some tweaks to process_proto_function() Jonathan Corbet
2025-07-03 15:48 ` Mauro Carvalho Chehab
2025-07-01 20:57 ` [PATCH 6/7] docs: kdoc: Remove a Python 2 comment Jonathan Corbet
2025-07-02 8:23 ` Jani Nikula
2025-07-03 15:49 ` Mauro Carvalho Chehab
2025-07-01 20:57 ` [PATCH 7/7] docs: kdoc: pretty up dump_enum() Jonathan Corbet
2025-07-03 15:57 ` Mauro Carvalho Chehab
2025-07-03 18:17 ` Jonathan Corbet
2025-07-03 22:29 ` Mauro Carvalho Chehab
2025-07-03 15:01 ` Akira Yokosawa [this message]
2025-07-03 18:20 ` [PATCH 0/7] Further kernel-doc tweakery Jonathan Corbet
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=e675d05d-0d81-47cc-b431-641b5b8c57b8@gmail.com \
--to=akiyks@gmail.com \
--cc=corbet@lwn.net \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mchehab+huawei@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