linux-hardening - Re: [PATCH v2 00/39] Implement kernel-doc in Python

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <87msea29ah.fsf@trenco.lwn.net>
Date: Mon, 24 Feb 2025 16:49:10 -0700
From: Jonathan Corbet <corbet@....net>
To: Mauro Carvalho Chehab <mchehab+huawei@...nel.org>, Linux Doc Mailing
 List <linux-doc@...r.kernel.org>
Cc: Mauro Carvalho Chehab <mchehab+huawei@...nel.org>, Mauro Carvalho Chehab
 <mchehab+huawei@...nel.org>, linux-kernel@...r.kernel.org, "Gustavo A. R.
 Silva" <mchehab+huawei@...nel.org>, Arnd Bergmann <arnd@...db.de>, Bingbu
 Cao <bingbu.cao@...el.com>, Greg Kroah-Hartman
 <gregkh@...uxfoundation.org>, Kees Cook <mchehab+huawei@...nel.org>,
 Sakari Ailus <sakari.ailus@...ux.intel.com>, Takashi Sakamoto
 <o-takashi@...amocchi.jp>, Tianshu Qiu <tian.shu.qiu@...el.com>,
 linux-arch@...r.kernel.org, linux-hardening@...r.kernel.org,
 linux-media@...r.kernel.org, linux-staging@...ts.linux.dev,
 linux1394-devel@...ts.sourceforge.net
Subject: Re: [PATCH v2 00/39] Implement kernel-doc in Python

Mauro Carvalho Chehab <mchehab+huawei@...nel.org> writes:

> Hi Jon,
>
> This changeset contains the kernel-doc.py script to replace the verable
> kernel-doc originally written in Perl. It replaces the first version and the
> second series I sent on the top of it.

I've sent minor comments on a couple of the patches.  The new version
works for me, I can't find any real problems with it.

Here's the question: what were your thoughts on when to do this?  I can
certainly take the initial fixup patches and get them out of your queue,
but at some point there will be a need to dive into the deep end.  I'm
just a bit leery of doing that as we head toward -rc5...  what do you
think of "just after the merge window"?

I'm definitely looking forward to no longer having to bash my head
against the Perl version...

Thanks,

jon