workflows.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Dragan Simic <dsimic@manjaro.org>
To: apw@canonical.com, joe@perches.com, corbet@lwn.net
Cc: dwaipayanray1@gmail.com, lukas.bulwahn@gmail.com,
	workflows@vger.kernel.org, linux-kernel@vger.kernel.org,
	linux-doc@vger.kernel.org, wens@csie.org, dsimic@manjaro.org
Subject: [PATCH v2 1/3] checkpatch: Make Helped-by tag supported
Date: Wed,  6 Nov 2024 07:28:40 +0100	[thread overview]
Message-ID: <0e1ef28710e3e49222c966f07958a9879fa4e903.1730874296.git.dsimic@manjaro.org> (raw)
In-Reply-To: <cover.1730874296.git.dsimic@manjaro.org>

Providing a Helped-by tag fits well to indicate someone had helped with the
development of a patch, to the level that still doesn't warrant providing
a Co-developed-by tag, but is much more than it would've been indicated by
providing a Suggested-by tag.  The Helped-by tag been already used recently
a few times in accepted patches. [1]

With all this in mind, let's have Helped-by supported in checkpatch.pl.

[1] https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/log/?qt=grep&q=Helped-by

Signed-off-by: Dragan Simic <dsimic@manjaro.org>
---
 scripts/checkpatch.pl | 1 +
 1 file changed, 1 insertion(+)

diff --git a/scripts/checkpatch.pl b/scripts/checkpatch.pl
index 4427572b2477..b89e62e9c2dd 100755
--- a/scripts/checkpatch.pl
+++ b/scripts/checkpatch.pl
@@ -622,6 +622,7 @@ our $signature_tags = qr{(?xi:
 	Reviewed-by:|
 	Reported-by:|
 	Suggested-by:|
+	Helped-by:|
 	To:|
 	Cc:
 )};

  reply	other threads:[~2024-11-06  6:29 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-11-06  6:28 [PATCH v2 0/3] " Dragan Simic
2024-11-06  6:28 ` Dragan Simic [this message]
2024-11-06  6:28 ` [PATCH v2 2/3] docs: submitting-patches: Reflow one short paragraph Dragan Simic
2024-11-06  6:28 ` [PATCH v2 3/3] docs: submitting-patches: Describe the use of Helped-by tag Dragan Simic
2024-11-06  6:47   ` Dragan Simic
2024-11-06 14:28 ` [PATCH v2 0/3] Make Helped-by tag supported Jonathan Corbet
2024-11-07 14:09   ` Dragan Simic
2024-11-08 19:12     ` Dan Williams
2024-11-09  3:10       ` Dragan Simic
2024-12-02 15:00         ` Dragan Simic
2024-12-02 17:11           ` Matthew Wilcox
2024-12-04  0:56             ` Shuah Khan

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=0e1ef28710e3e49222c966f07958a9879fa4e903.1730874296.git.dsimic@manjaro.org \
    --to=dsimic@manjaro.org \
    --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=wens@csie.org \
    --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