linux-kernel - Re: [PATCH v2 00/10] Collect documentation-related tools under /tools/docs

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: <123ab038-39b8-4632-9090-2c95cbc0130a@gmail.com>
Date: Fri, 24 Oct 2025 22:55:36 +0900
From: Akira Yokosawa <akiyks@...il.com>
To: Jonathan Corbet <corbet@....net>, linux-doc@...r.kernel.org
Cc: linux-kernel@...r.kernel.org,
 Mauro Carvalho Chehab <mchehab+huawei@...nel.org>,
 Randy Dunlap <rdunlap@...radead.org>,
 Jani Nikula <jani.nikula@...ux.intel.com>
Subject: Re: [PATCH v2 00/10] Collect documentation-related tools under
 /tools/docs

On Fri, 24 Oct 2025 12:10:54 +0900, Akira Yokosawa wrote:
> Hi Jon,
> 
> On Thu, 23 Oct 2025 10:10:08 -0600, Jonathan Corbet wrote:
>> Our documentation-related tools are spread out over various directories;
>> several are buried in the scripts/ dumping ground.  That makes them harder
>> to discover and harder to maintain.
>>
>> Recently, the idea of creating a dedicated directory for documentation tools
>> came up; I decided to see what it would look like.  This series creates a
>> new directory, tools/docs, and moves various utilities there, hopefully
>> fixing up all of the relevant references in the process.
>>
>> At the end, rather than move the old, Perl kernel-doc, I simply removed it.
>>
>> The big elephant lurking in this small room is the home for Python modules;
>> I left them under scripts/lib, but that is an even less appropriate place
>> than it was before.  I would propose either tools/python or lib/python;
>> thoughts on that matter welcome.
>>
>> Changes in v2:
>>   - Rebase on top of all of Mauro's changes (the most painful rebase I've
>>     ever done, I think).
> 
> I tried to apply this series on top of current docs-next, and several earlier
> merge points, but haven't succeeded so far, even with "git am -3" ...
> 
> Where am I supposed to apply this?

OK, I have finally figured that out.
This can be applied on top of merge commit ee9a66919354 ("Merge branch
'mauro-pdf' into docs-mw"), dated back more than two months !

I suspect v2 is not what you had planned to submit ... ?

        Thanks, Akira