public inbox for linux-kernel-mentees@lists.linux-foundation.org
 help / color / mirror / Atom feed
From: "Ignacio Peña" <ignacio.pena87@gmail.com>
To: linux-kernel-mentees@lists.linuxfoundation.org
Subject: [ANNOUNCE] kernel-patch-validator - Tool to validate patches before submission
Date: Thu, 17 Jul 2025 03:54:17 -0400	[thread overview]
Message-ID: <20250717075417.8597-1-ignacio.pena87@gmail.com> (raw)

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)
- Missing changelog in v2+ patches after --- marker  
- Multiple logical changes in one patch
- Wrong Signed-off-by format

The tool includes additional scripts:
- find-bugs.sh: Finds spelling errors, checkpatch issues
- test-patch.sh: Safe testing workflow
- contribution-checklist.sh: Readiness assessment

Each check is based on actual rejection feedback. Hope this helps other
newcomers avoid the same mistakes.

Feedback and contributions welcome!

Thanks,
Ignacio Peña

             reply	other threads:[~2025-07-17  7:54 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-07-17  7:54 Ignacio Peña [this message]
2025-07-17 12:15 ` [ANNOUNCE] kernel-patch-validator - Tool to validate patches before submission Greg KH
     [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=20250717075417.8597-1-ignacio.pena87@gmail.com \
    --to=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