linux-hardening - Re: [PATCH v3 00/33] 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: <87ecxubuwm.fsf@trenco.lwn.net>
Date: Mon, 14 Apr 2025 09:54:49 -0600
From: Jonathan Corbet <corbet@....net>
To: Andy Shevchenko <andriy.shevchenko@...el.com>
Cc: Mauro Carvalho Chehab <mchehab+huawei@...nel.org>, Linux Doc Mailing
 List <linux-doc@...r.kernel.org>, linux-kernel@...r.kernel.org, "Gustavo
 A. R. Silva" <gustavoars@...nel.org>, Kees Cook <kees@...nel.org>, Russell
 King <linux@...linux.org.uk>, linux-hardening@...r.kernel.org,
 netdev@...r.kernel.org
Subject: Re: [PATCH v3 00/33] Implement kernel-doc in Python

> Andy Shevchenko <andriy.shevchenko@...el.com> writes:
>
>> On Wed, Apr 09, 2025 at 12:30:00PM -0600, Jonathan Corbet wrote:
>>> Mauro Carvalho Chehab <mchehab+huawei@...nel.org> writes:
>>> 
>>> > 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.
>>> 
>>> OK, I've applied it, looked at the (minimal) changes in output, and
>>> concluded that it's good - all this stuff is now in docs-next.  Many
>>> thanks for doing this!
>>> 
>>> I'm going to hold off on other documentation patches for a day or two
>>> just in case anything turns up.  But it looks awfully good.
>>
>> This started well, until it becomes a scripts/lib/kdoc.
>> So, it makes the `make O=...` builds dirty *). Please make sure this doesn't leave
>> "disgusting turd" )as said by Linus) in the clean tree.
>>
>> *) it creates that __pycache__ disaster. And no, .gitignore IS NOT a solution.

Actually, I find myself unable to reproduce this; can you tell me how
you get Python to create that directory on your system?  Which version
of Python?

Thanks,

jon