workflows.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Konstantin Ryabitsev <konstantin@linuxfoundation.org>
To: Brendan Jackman <jackmanb@google.com>
Cc: 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>,
	linux-kernel@vger.kernel.org, workflows@vger.kernel.org,
	 linux-doc@vger.kernel.org
Subject: Re: [PATCH 1/2] checkpatch: Add support for Checkpatch-ignore patch footer
Date: Tue, 14 Jan 2025 08:34:01 -0500	[thread overview]
Message-ID: <5abiddu5zgxdmotauxnohnk25zyzd3cbjlfgskejk5ta7arzk2@pjpofoy7pcce> (raw)
In-Reply-To: <20250113-checkpatch-ignore-v1-1-63a7a740f568@google.com>

On Mon, Jan 13, 2025 at 04:04:22PM +0000, Brendan Jackman wrote:
> 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.
> 
> To avoid significant reworks to the Perl code, this is implemented by
> mutating a global variable while processing each patch. (The variable
> name refers to a patch as a "file" for consistency with other code).
> 
> This feature is immediately adopted for this commit itself, which
> falls afoul of EMAIL_SUBJECT due to the word "checkpatch" appearing in
> the "Checkpatch-ignore" reference in the title - a good example of a
> false positive.
> 
> [0] b4 - see "--check" arg
>     https://b4.docs.kernel.org/en/latest/contributor/prep.html
> 
> Checkpatch-ignore: EMAIL_SUBJECT
> Signed-off-by: Brendan Jackman <jackmanb@google.com>

Do we really want this to become part of the permanent commit message? I'm
pretty sure this won't go over well with many.

-K

  parent reply	other threads:[~2025-01-14 13:34 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-01-13 16:04 [PATCH 0/2] " Brendan Jackman
2025-01-13 16:04 ` [PATCH 1/2] " 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 [this message]
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=5abiddu5zgxdmotauxnohnk25zyzd3cbjlfgskejk5ta7arzk2@pjpofoy7pcce \
    --to=konstantin@linuxfoundation.org \
    --cc=apw@canonical.com \
    --cc=corbet@lwn.net \
    --cc=dwaipayanray1@gmail.com \
    --cc=jackmanb@google.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