From: Randy Dunlap <rdunlap@infradead.org>
To: Mauro Carvalho Chehab <mchehab+huawei@kernel.org>,
Linux Doc Mailing List <linux-doc@vger.kernel.org>,
Jonathan Corbet <corbet@lwn.net>
Cc: linux-kernel@vger.kernel.org, Arnd Bergmann <arnd@arndb.de>,
linux-arch@vger.kernel.org, linux-hardening@vger.kernel.org
Subject: Re: [PATCH RFCv2 0/5]Implement kernel-doc in Python
Date: Thu, 13 Feb 2025 19:15:28 -0800 [thread overview]
Message-ID: <6958d7a5-2403-423d-a0a3-0c43931a7d30@infradead.org> (raw)
In-Reply-To: <cover.1739447912.git.mchehab+huawei@kernel.org>
Hi Mauro,
On 2/13/25 4:06 AM, Mauro Carvalho Chehab wrote:
> Hi Jon,
>
> That's the second version of the Python kernel-doc tool.
>
> As the previous version, I tried to stay as close as possible of the original
> Perl implementation, as it helps to double check if each function was
> properly translated to Python. This have been helpful debugging troubles
> that happened during the conversion.
Since this new version is supposed to be bug-for-bug compatible, I will wait
until later to test the current known bugs that I know about in (Perl) kernel-doc.
For a preview of most of them, you can read:
https://lore.kernel.org/linux-doc/3a6a7dd0-72f1-44c6-b0bc-b1ce76fca76a@infradead.org/
and its follow-up email (today).
There are quite a few problems with parsing function parameters that use
typedefs.
--
~Randy
next prev parent reply other threads:[~2025-02-14 3:15 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-13 12:06 [PATCH RFCv2 0/5]Implement kernel-doc in Python Mauro Carvalho Chehab
2025-02-13 12:06 ` [PATCH RFCv2 1/5] include/asm-generic/io.h: fix kerneldoc markup Mauro Carvalho Chehab
2025-02-13 12:16 ` Arnd Bergmann
2025-02-14 3:15 ` Randy Dunlap [this message]
2025-02-14 8:02 ` [PATCH RFCv2 0/5]Implement kernel-doc in Python 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=6958d7a5-2403-423d-a0a3-0c43931a7d30@infradead.org \
--to=rdunlap@infradead.org \
--cc=arnd@arndb.de \
--cc=corbet@lwn.net \
--cc=linux-arch@vger.kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-hardening@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