mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Breno Rodrigues Alves <breno3011alves@gmail.com>
To: Jonathan Corbet <corbet@lwn.net>
Cc: Heiko Carstens <hca@linux.ibm.com>,
	linux-kernel@vger.kernel.org, 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 remaining Perl utilities in scripts/
Date: Mon, 19 Oct 2026 12:39:31 -0300	[thread overview]
Message-ID: <20261019153932.27283-1-breno3011alves@gmail.com> (raw)
In-Reply-To: <87wlrd932j.fsf@trenco.lwn.net>

Hi Jon,

Thank you for the detailed and direct feedback. You are absolutely
right, and I appreciate you taking the time to correct my
misunderstandings.

Regarding get_maintainer and checkpatch: I was completely mistaken. I
conflated the ongoing discussions and RFC proposals with the existing
state of the kernel. I apologize for the inaccuracy.

Your point about the maintenance burden and the "consistency" argument
is very well taken. I see now that "consistency" is not a valid
technical justification if there are no active bugs or integration
requirements (like Sphinx for kerneldoc). As you noted, people running
the scripts do not care about the implementation language, and I do not
have the track record yet to offer myself as a replacement maintainer
for these tools.

I realize that my v2 patch for checkstack.py falls into the "change for
its own sake" category you described. Since the Perl script works and
has a stable maintenance status, submitting this patch was premature.

I will withdraw the checkstack patch. Please disregard the [PATCH v2]
sent earlier. I want to contribute meaningfully to the kernel, but
clearly, I need to focus on fixing actual bugs or making changes with a
clear, undeniable technical necessity.

Thank you again for the guidance. It is a lesson I will not forget.

Best regards,
Breno

  reply	other threads:[~2026-10-19 15:39 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20261019100505.3199861A74+hca@linux.ibm.com>
2026-10-19 13:34 ` Breno Rodrigues Alves
2026-10-19 14:29   ` Jonathan Corbet
2026-10-19 15:39     ` Breno Rodrigues Alves [this message]
2026-10-18 11:28 Breno Rodrigues Alves

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=20261019153932.27283-1-breno3011alves@gmail.com \
    --to=breno3011alves@gmail.com \
    --cc=apw@canonical.com \
    --cc=corbet@lwn.net \
    --cc=dwaipayanray1@gmail.com \
    --cc=hca@linux.ibm.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®