From: Greg KH <gregkh@linuxfoundation.org>
To: "Ignacio Peña" <ignacio.pena87@gmail.com>
Cc: linux-kernel-mentees@lists.linuxfoundation.org
Subject: Re: [ANNOUNCE] kernel-patch-validator - Tool to validate patches before submission
Date: Thu, 17 Jul 2025 18:34:13 +0200 [thread overview]
Message-ID: <2025071741-pregnant-punctured-f1fb@gregkh> (raw)
In-Reply-To: <20250717162936.23035-1-ignacio.pena87@gmail.com>
On Thu, Jul 17, 2025 at 12:29:36PM -0400, Ignacio Peña wrote:
> Would you prefer if I start with small individual patches to checkpatch.pl
> for each check, or should I put together an RFC first to discuss which
> checks would be most valuable to integrate?
Just send patches, like normal. "RFC" doesn't work for when you don't
have working patches to start with.
thanks,
greg k-h
next prev parent reply other threads:[~2025-07-17 16:34 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <ZppSfKGao4PQvRJd@kroah.com>
2025-07-17 16:29 ` [ANNOUNCE] kernel-patch-validator - Tool to validate patches before submission Ignacio Peña
2025-07-17 16:34 ` Greg KH [this message]
2025-07-17 7:54 Ignacio Peña
2025-07-17 12:15 ` Greg KH
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=2025071741-pregnant-punctured-f1fb@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=ignacio.pena87@gmail.com \
--cc=linux-kernel-mentees@lists.linuxfoundation.org \
/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