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 14:15:50 +0200 [thread overview]
Message-ID: <2025071717-quadrant-rentable-e8e9@gregkh> (raw)
In-Reply-To: <20250717075417.8597-1-ignacio.pena87@gmail.com>
On Thu, Jul 17, 2025 at 03:54:17AM -0400, Ignacio Peña wrote:
> Hi everyone,
>
> After getting patches rejected multiple times for common mistakes, I built
> a tool to validate patches before submission. It catches issues that
> frequently lead to rejections.
>
> Features:
> - 21+ automated checks based on real maintainer feedback
> - Validates format, DCO, changelog placement, dates
> - Integrated checkpatch.pl with enhanced reporting
> - Tools to find first contributions (find-bugs.sh)
> - Patch series validation
>
> Available at: https://github.com/ipenas-cl/kernel-patch-validator
>
> Quick usage:
> $ git format-patch -1
> $ validate-patch.sh 0001-your-patch.patch
>
> Example issues it catches:
> - Future dates (2025 bug from wrong system clock)
Note, it is now 2025, so this check keeps failing :)
Overall, I like the idea, the implementation needs a bit of work, see
the few github issues I opened on it for details found in my testing.
Can you add some of these checks to checkpatch.pl itself? That would be
the best thing to do in the end. Having to use different tools makes
things harder to keep in sync and to remember to use at all.
thanks,
greg k-h
next prev parent reply other threads:[~2025-07-17 12:15 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-17 7:54 [ANNOUNCE] kernel-patch-validator - Tool to validate patches before submission Ignacio Peña
2025-07-17 12:15 ` Greg KH [this message]
[not found] <ZppSfKGao4PQvRJd@kroah.com>
2025-07-17 16:29 ` Ignacio Peña
2025-07-17 16:34 ` 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=2025071717-quadrant-rentable-e8e9@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