[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20230801170255.163237-24-jim.cromie@gmail.com>
Date: Tue, 1 Aug 2023 11:02:55 -0600
From: Jim Cromie <jim.cromie@...il.com>
To: daniel.vetter@...ll.ch, daniel@...ll.ch, jbaron@...mai.com,
gregkh@...uxfoundation.org, linux-kernel@...r.kernel.org,
dri-devel@...ts.freedesktop.org, amd-gfx@...ts.freedesktop.org,
intel-gvt-dev@...ts.freedesktop.org,
intel-gfx@...ts.freedesktop.org
Cc: linux@...musvillemoes.dk, joe@...ches.com, jani.nikula@...el.com,
ville.syrjala@...ux.intel.com, seanpaul@...omium.org,
robdclark@...il.com, Jim Cromie <jim.cromie@...il.com>,
apw@...onical.com
Subject: [PATCH v5 22/22] checkpatch: reword long-line warn about commit-msg
Reword the warning to complain about line length 1st, since thats
whats actually tested.
Cc: apw@...onical.com
Cc: joe@...ches.com
Signed-off-by: Jim Cromie <jim.cromie@...il.com>
---
scripts/checkpatch.pl | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/scripts/checkpatch.pl b/scripts/checkpatch.pl
index f6b6b2a50dfe..31c55e3ece09 100755
--- a/scripts/checkpatch.pl
+++ b/scripts/checkpatch.pl
@@ -3272,7 +3272,7 @@ sub process {
# A Fixes:, link or signature tag line
$commit_log_possible_stack_dump)) {
WARN("COMMIT_LOG_LONG_LINE",
- "Possible unwrapped commit description (prefer a maximum 75 chars per line)\n" . $herecurr);
+ "Prefer a maximum 75 chars per line (possible unwrapped commit description?)\n" . $herecurr);
$commit_log_long_line = 1;
}
--
2.41.0
Powered by blists - more mailing lists