From: Andrew Morton <akpm@linux-foundation.org>
To: mm-commits@vger.kernel.org,linux@treblig.org,joe@perches.com,akpm@linux-foundation.org
Subject: [merged mm-nonmm-stable] checkpatch-allow-http-links-of-any-length-in-commit-logs.patch removed from -mm tree
Date: Sat, 13 Sep 2025 17:35:08 -0700 [thread overview]
Message-ID: <20250914003508.C3172C4CEEB@smtp.kernel.org> (raw)
The quilt patch titled
Subject: checkpatch: allow http links of any length in commit logs
has been removed from the -mm tree. Its filename was
checkpatch-allow-http-links-of-any-length-in-commit-logs.patch
This patch was dropped because it was merged into the mm-nonmm-stable branch
of git://git.kernel.org/pub/scm/linux/kernel/git/akpm/mm
------------------------------------------------------
From: Joe Perches <joe@perches.com>
Subject: checkpatch: allow http links of any length in commit logs
Date: Sat, 09 Aug 2025 21:31:10 -0700
Dave Gilbert noticed that checkpatch warns about URL links over 75 chars
in length in commit logs.
Fix that.
Link: https://lkml.kernel.org/r/3529faaf84a5a9a96c5c0ec4183ae0ba6e97673c.camel@perches.com
Signed-off-by: Joe Perches <joe@perches.com>
Cc: Dave Gilbert <linux@treblig.org>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
---
scripts/checkpatch.pl | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
--- a/scripts/checkpatch.pl~checkpatch-allow-http-links-of-any-length-in-commit-logs
+++ a/scripts/checkpatch.pl
@@ -3294,7 +3294,7 @@ sub process {
# file delta changes
$line =~ /^\s*(?:[\w\.\-\+]*\/)++[\w\.\-\+]+:/ ||
# filename then :
- $line =~ /^\s*(?:Fixes:|$link_tags_search|$signature_tags)/i ||
+ $line =~ /^\s*(?:Fixes:|https?:|$link_tags_search|$signature_tags)/i ||
# A Fixes:, link or signature tag line
$commit_log_possible_stack_dump)) {
WARN("COMMIT_LOG_LONG_LINE",
_
Patches currently in -mm which might be from joe@perches.com are
reply other threads:[~2025-09-14 0:35 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20250914003508.C3172C4CEEB@smtp.kernel.org \
--to=akpm@linux-foundation.org \
--cc=joe@perches.com \
--cc=linux@treblig.org \
--cc=mm-commits@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 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.