mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Breno Rodrigues Alves <breno3011alves@gmail.com>
To: linux-kernel@vger.kernel.org
Cc: 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: Sun, 18 Oct 2026 20:19:16 -0300	[thread overview]
Message-ID: <20261018231917.74657-1-breno3011alves@gmail.com> (raw)
In-Reply-To: <87fqy2afnk.fsf@trenco.lwn.net>

> 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.

I ran a quick analysis of each script to separate what's actually
used from what's likely dead code. Three groups:

1. Actively used by developers or build:
   - get_maintainer.pl: 28 references in Documentation/ alone.
   - recordmcount.pl: called from scripts/Makefile.build when
     CONFIG_FTRACE_MCOUNT_USE_RECORDMCOUNT is enabled.
   - generate_initcall_order.pl: called from scripts/Makefile.build
     when initcall tracing is enabled.

2. Used by developers, not integrated into the build:
   - leaking_addresses.pl: security-research tool run manually.

3. Likely obsolete:
   - checkdeclares.pl: no build, doc, or in-tree references.
     (Last-modified not verified locally — shallow clone — but no
     reference is the stronger signal.)
   - checkversion.pl: one reference in scripts/Makefile.build, but
     the check itself is narrow.
   - extract_xc3028.pl: no references; extracts firmware for DVB
     hardware unmaintained for over a decade.

The honest conclusion is that group 3 is a removal candidate, not
a conversion target. I did not do this analysis before v1 and I
should have.

Plan for v2:
  - Keep get_maintainer, recordmcount, generate_initcall_order,
    leaking_addresses.
  - Drop checkdeclares and extract_xc3028 from the series.
  - Decide checkversion separately (keep, or propose for removal
    after a public call for users).
  - Rewrite the cover letter to state the motivation explicitly.

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.

Breno

  reply	other threads:[~2026-10-18 23:19 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-18 11:06 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 [this message]
2026-10-19 10:05     ` Heiko Carstens

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=20261018231917.74657-1-breno3011alves@gmail.com \
    --to=breno3011alves@gmail.com \
    --cc=apw@canonical.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®