From: Petr Vorel <pvorel@suse.cz>
To: cryolitia@uniontech.com
Cc: Andy Whitcroft <apw@canonical.com>, Joe Perches <joe@perches.com>,
Dwaipayan Ray <dwaipayanray1@gmail.com>,
Lukas Bulwahn <lukas.bulwahn@gmail.com>,
Cryolitia PukNgae via B4 Relay
<devnull+cryolitia.uniontech.com@kernel.org>,
linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-mm@kvack.org, workflows@vger.kernel.org,
niecheng1@uniontech.com, ltp@lists.linux.it,
zhanjun@uniontech.com
Subject: Re: [LTP] [PATCH RESEND v2] checkpatch: Suppress warnings when Reported-by: is followed by Link:
Date: Thu, 15 Jan 2026 08:22:31 +0100 [thread overview]
Message-ID: <20260115072231.GA438294@pevik> (raw)
In-Reply-To: <20260113-checkpatch-v2-1-5dfe8b9f4d90@uniontech.com>
Hi Cryolitia,
> From: Cryolitia PukNgae <cryolitia@uniontech.com>
> > The tag should be followed by a Closes: tag pointing to the report,
> > unless the report is not available on the web. The Link: tag can be
> > used instead of Closes: if the patch fixes a part of the issue(s)
> > being reported.
Indeed, this is true, although there is a prerequisite:
The Link: tag can be used instead of Closes: if the patch fixes a part of
the issue(s) being reported.
Reviewed-by: Petr Vorel <pvorel@suse.cz>
I also see you Cc LTP ML. FYI we vendored scripts/checkpatch.pl (with occasional
updates).
Kind regards,
Petr
> Accroding to Documentation/process/submitting-patches.rst , Link: is
> also acceptable to followed a Reported-by:
> Signed-off-by: Cryolitia PukNgae <cryolitia@uniontech.com>
> ---
> Link to previous: https://lore.kernel.org/r/20251023-checkpatch-v1-1-ff73ed1027d6@uniontech.com
> ---
> scripts/checkpatch.pl | 6 +++---
> 1 file changed, 3 insertions(+), 3 deletions(-)
> diff --git a/scripts/checkpatch.pl b/scripts/checkpatch.pl
> index c0250244cf7a..dac9d98133c6 100755
> --- a/scripts/checkpatch.pl
> +++ b/scripts/checkpatch.pl
> @@ -3209,10 +3209,10 @@ sub process {
> if ($sign_off =~ /^reported(?:|-and-tested)-by:$/i) {
> if (!defined $lines[$linenr]) {
> WARN("BAD_REPORTED_BY_LINK",
> - "Reported-by: should be immediately followed by Closes: with a URL to the report\n" . $herecurr . "\n");
> - } elsif ($rawlines[$linenr] !~ /^closes:\s*/i) {
> + "Reported-by: should be immediately followed by Closes: or Link: with a URL to the report\n" . $herecurr . "\n");
> + } elsif ($rawlines[$linenr] !~ /^(closes|link):\s*/i) {
> WARN("BAD_REPORTED_BY_LINK",
> - "Reported-by: should be immediately followed by Closes: with a URL to the report\n" . $herecurr . $rawlines[$linenr] . "\n");
> + "Reported-by: should be immediately followed by Closes: or Link: with a URL to the report\n" . $herecurr . $rawlines[$linenr] . "\n");
> }
> }
> }
WARNING: multiple messages have this Message-ID (diff)
From: Petr Vorel <pvorel@suse.cz>
To: cryolitia@uniontech.com
Cc: Cryolitia PukNgae via B4 Relay
<devnull+cryolitia.uniontech.com@kernel.org>,
linux-doc@vger.kernel.org,
Dwaipayan Ray <dwaipayanray1@gmail.com>,
linux-kernel@vger.kernel.org, linux-mm@kvack.org,
Joe Perches <joe@perches.com>,
workflows@vger.kernel.org, Andy Whitcroft <apw@canonical.com>,
Lukas Bulwahn <lukas.bulwahn@gmail.com>,
niecheng1@uniontech.com, ltp@lists.linux.it,
zhanjun@uniontech.com
Subject: Re: [LTP] [PATCH RESEND v2] checkpatch: Suppress warnings when Reported-by: is followed by Link:
Date: Thu, 15 Jan 2026 08:22:31 +0100 [thread overview]
Message-ID: <20260115072231.GA438294@pevik> (raw)
In-Reply-To: <20260113-checkpatch-v2-1-5dfe8b9f4d90@uniontech.com>
Hi Cryolitia,
> From: Cryolitia PukNgae <cryolitia@uniontech.com>
> > The tag should be followed by a Closes: tag pointing to the report,
> > unless the report is not available on the web. The Link: tag can be
> > used instead of Closes: if the patch fixes a part of the issue(s)
> > being reported.
Indeed, this is true, although there is a prerequisite:
The Link: tag can be used instead of Closes: if the patch fixes a part of
the issue(s) being reported.
Reviewed-by: Petr Vorel <pvorel@suse.cz>
I also see you Cc LTP ML. FYI we vendored scripts/checkpatch.pl (with occasional
updates).
Kind regards,
Petr
> Accroding to Documentation/process/submitting-patches.rst , Link: is
> also acceptable to followed a Reported-by:
> Signed-off-by: Cryolitia PukNgae <cryolitia@uniontech.com>
> ---
> Link to previous: https://lore.kernel.org/r/20251023-checkpatch-v1-1-ff73ed1027d6@uniontech.com
> ---
> scripts/checkpatch.pl | 6 +++---
> 1 file changed, 3 insertions(+), 3 deletions(-)
> diff --git a/scripts/checkpatch.pl b/scripts/checkpatch.pl
> index c0250244cf7a..dac9d98133c6 100755
> --- a/scripts/checkpatch.pl
> +++ b/scripts/checkpatch.pl
> @@ -3209,10 +3209,10 @@ sub process {
> if ($sign_off =~ /^reported(?:|-and-tested)-by:$/i) {
> if (!defined $lines[$linenr]) {
> WARN("BAD_REPORTED_BY_LINK",
> - "Reported-by: should be immediately followed by Closes: with a URL to the report\n" . $herecurr . "\n");
> - } elsif ($rawlines[$linenr] !~ /^closes:\s*/i) {
> + "Reported-by: should be immediately followed by Closes: or Link: with a URL to the report\n" . $herecurr . "\n");
> + } elsif ($rawlines[$linenr] !~ /^(closes|link):\s*/i) {
> WARN("BAD_REPORTED_BY_LINK",
> - "Reported-by: should be immediately followed by Closes: with a URL to the report\n" . $herecurr . $rawlines[$linenr] . "\n");
> + "Reported-by: should be immediately followed by Closes: or Link: with a URL to the report\n" . $herecurr . $rawlines[$linenr] . "\n");
> }
> }
> }
--
Mailing list info: https://lists.linux.it/listinfo/ltp
next prev parent reply other threads:[~2026-01-15 7:22 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-13 3:22 [PATCH RESEND v2] checkpatch: Suppress warnings when Reported-by: is followed by Link: Cryolitia PukNgae
2026-01-13 3:22 ` [LTP] " Cryolitia PukNgae via B4 Relay via ltp
2026-01-13 3:22 ` Cryolitia PukNgae via B4 Relay
2026-01-15 7:22 ` Petr Vorel [this message]
2026-01-15 7:22 ` [LTP] " Petr Vorel
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=20260115072231.GA438294@pevik \
--to=pvorel@suse.cz \
--cc=apw@canonical.com \
--cc=cryolitia@uniontech.com \
--cc=devnull+cryolitia.uniontech.com@kernel.org \
--cc=dwaipayanray1@gmail.com \
--cc=joe@perches.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=ltp@lists.linux.it \
--cc=lukas.bulwahn@gmail.com \
--cc=niecheng1@uniontech.com \
--cc=workflows@vger.kernel.org \
--cc=zhanjun@uniontech.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.