linux-kernel - Re: [PATCH 01/13] docs: Move the "features" tools to tools/doc

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: <a18c897e-8679-4155-932e-4bdb9e37f25c@infradead.org>
Date: Wed, 13 Aug 2025 16:42:42 -0700
From: Randy Dunlap <rdunlap@...radead.org>
To: Mauro Carvalho Chehab <mchehab+huawei@...nel.org>,
 Jonathan Corbet <corbet@....net>
Cc: linux-doc@...r.kernel.org, linux-kernel@...r.kernel.org,
 Akira Yokosawa <akiyks@...il.com>
Subject: Re: [PATCH 01/13] docs: Move the "features" tools to tools/doc



On 8/13/25 4:38 PM, Mauro Carvalho Chehab wrote:
> Em Wed, 13 Aug 2025 15:32:00 -0600
> Jonathan Corbet <corbet@....net> escreveu:
> 
>> The scripts for managing the features docs are found in three different
>> directories; unite them all under tools/doc and update references as
>> needed.
>>
>> Signed-off-by: Jonathan Corbet <corbet@....net>
>> ---
>>  Documentation/sphinx/kernel_feat.py                           | 4 ++--
>>  .../features/scripts => tools/doc}/features-refresh.sh        | 0
>>  {scripts => tools/doc}/get_feat.pl                            | 2 +-
> 
> This one is the next on my list to convert to Python, but I didn't
> do any changes on it yet.

Just curious, why does it need to be converted from shell to Python?
I'm sure you will explain that in the patch description (or cover letter).

> So,
> 
> Reviewed-by: Mauro Carvalho Chehab <mchehab+huawei@...nel.org>
> 
> 
>>  {Documentation/features => tools/doc}/list-arch.sh            | 2 +-
>>  4 files changed, 4 insertions(+), 4 deletions(-)
>>  rename {Documentation/features/scripts => tools/doc}/features-refresh.sh (100%)
>>  rename {scripts => tools/doc}/get_feat.pl (99%)
>>  rename {Documentation/features => tools/doc}/list-arch.sh (83%)
> 
> I wonder if the best wouldn't be to have a single script for
> features handling all usecases.


-- 
~Randy