From: Brendan Jackman <jackmanb@google.com>
To: Andy Whitcroft <apw@canonical.com>, Joe Perches <joe@perches.com>,
Dwaipayan Ray <dwaipayanray1@gmail.com>,
Lukas Bulwahn <lukas.bulwahn@gmail.com>,
Jonathan Corbet <corbet@lwn.net>
Cc: linux-kernel@vger.kernel.org, workflows@vger.kernel.org,
linux-doc@vger.kernel.org, Brendan Jackman <jackmanb@google.com>
Subject: [PATCH 0/2] checkpatch: Add support for Checkpatch-ignore patch footer
Date: Mon, 13 Jan 2025 16:04:21 +0000 [thread overview]
Message-ID: <20250113-checkpatch-ignore-v1-0-63a7a740f568@google.com> (raw)
Checkpatch sometimes has false positives. This makes it less useful for
automatic usage: tools like b4 [0] can run checkpatch on all of your
patches and give you a quick overview. When iterating on a branch, it's
tiresome to manually re-check that any errors are known false positives.
This patch adds a feature to record in the commit message that a patch
might produce a certain checkpatch error, and that this is an expected
false positive. Recording this information in the patch itself can also
highlight it to reviewers, so they can make a judgment as to whether
it's appropriate to ignore.
Signed-off-by: Brendan Jackman <jackmanb@google.com>
---
Brendan Jackman (2):
checkpatch: Add support for Checkpatch-ignore patch footer
docs: checkpatch: Document Checkpatch-ignore patch footer
Documentation/dev-tools/checkpatch.rst | 9 ++++++++-
scripts/checkpatch.pl | 11 ++++++++++-
2 files changed, 18 insertions(+), 2 deletions(-)
---
base-commit: eae581be230bec00287807017839b3b2cd83f9ff
change-id: 20250113-checkpatch-ignore-1096914844eb
Best regards,
--
Brendan Jackman <jackmanb@google.com>
next reply other threads:[~2025-01-13 16:04 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-13 16:04 Brendan Jackman [this message]
2025-01-13 16:04 ` [PATCH 1/2] checkpatch: Add support for Checkpatch-ignore patch footer Brendan Jackman
2025-01-13 19:15 ` Joe Perches
2025-01-14 11:42 ` Brendan Jackman
2025-01-14 11:43 ` Brendan Jackman
2025-01-14 13:34 ` Konstantin Ryabitsev
2025-01-14 14:25 ` Brendan Jackman
2025-01-14 16:04 ` Konstantin Ryabitsev
2025-01-14 18:29 ` Brendan Jackman
2025-01-14 19:26 ` Konstantin Ryabitsev
2025-01-15 9:58 ` Brendan Jackman
2025-01-13 16:04 ` [PATCH 2/2] docs: checkpatch: Document " Brendan Jackman
2025-01-13 16:20 ` [PATCH 0/2] checkpatch: Add support for " Matthew Wilcox
2025-01-13 17:11 ` Brendan Jackman
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=20250113-checkpatch-ignore-v1-0-63a7a740f568@google.com \
--to=jackmanb@google.com \
--cc=apw@canonical.com \
--cc=corbet@lwn.net \
--cc=dwaipayanray1@gmail.com \
--cc=joe@perches.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lukas.bulwahn@gmail.com \
--cc=workflows@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).