From: Heiko Carstens <hca@linux.ibm.com>
To: Breno Rodrigues Alves <breno3011alves@gmail.com>
Cc: linux-kernel@vger.kernel.org, Jonathan Corbet <corbet@lwn.net>,
Andy Whitcroft <apw@canonical.com>, Joe Perches <joe@perches.com>,
Dwaipayan Ray <dwaipayanray1@gmail.com>,
Lukas Bulwahn <lukas.bulwahn@gmail.com>
Subject: Re: [RFC PATCH 0/7] scripts: convert seven more Perl utilities to Python
Date: Mon, 19 Oct 2026 12:05:05 +0200 [thread overview]
Message-ID: <20261019100505.3199861A74-hca@linux.ibm.com> (raw)
In-Reply-To: <20261018231917.74657-1-breno3011alves@gmail.com>
On Sun, Oct 18, 2026 at 08:19:16PM -0300, Breno Rodrigues Alves wrote:
> > So an important part of describing any change is *why* you are doing it.
> > Why are you doing all of these conversions? Some of these scripts have
> > not seen changes in decades and are likely unused; why do we want to
> > mess with them now?
>
> You're right, and thanks for pushing on this — I should have framed
> the *why* in the cover letter.
...
> Broader motivation for the kept four: kernel CI and tooling
> already assume Python for kernel-doc, spdxcheck, bpf_doc.
> Keeping Perl alive solely for a handful of scripts forces two
> runtimes for the same class of tools. Converting the active ones
> closes that gap; converting dead ones does not.
That is an odd reason - if I'm not wrong then you have zero upstream
commits, and now are proposing fundamental changes to tools maintained
and used by others? I guess this is 100% LLM work(?).
prev parent reply other threads:[~2026-10-19 10:05 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-18 11:06 [RFC PATCH 0/7] scripts: convert seven more Perl utilities to Python Breno Rodrigues Alves
2026-10-18 11:06 ` [RFC PATCH 1/7] scripts: convert checkdeclares.pl " Breno Rodrigues Alves
2026-10-18 11:06 ` [RFC PATCH 2/7] scripts: convert checkversion.pl " Breno Rodrigues Alves
2026-10-18 11:06 ` [RFC PATCH 3/7] scripts: convert extract_xc3028.pl " Breno Rodrigues Alves
2026-10-18 11:06 ` [RFC PATCH 4/7] scripts: convert generate_initcall_order.pl " Breno Rodrigues Alves
2026-10-18 11:06 ` [RFC PATCH 5/7] scripts: convert get_maintainer.pl " Breno Rodrigues Alves
2026-10-18 11:06 ` [RFC PATCH 6/7] scripts: convert leaking_addresses.pl " Breno Rodrigues Alves
2026-10-18 11:06 ` [RFC PATCH 7/7] scripts: convert recordmcount.pl " Breno Rodrigues Alves
2026-10-18 20:59 ` [RFC PATCH 0/7] scripts: convert seven more Perl utilities " Jonathan Corbet
2026-10-18 23:19 ` Breno Rodrigues Alves
2026-10-19 10:05 ` Heiko Carstens [this message]
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=20261019100505.3199861A74-hca@linux.ibm.com \
--to=hca@linux.ibm.com \
--cc=apw@canonical.com \
--cc=breno3011alves@gmail.com \
--cc=corbet@lwn.net \
--cc=dwaipayanray1@gmail.com \
--cc=joe@perches.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lukas.bulwahn@gmail.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.