[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-Id: <20220905104542.2368950-1-dmitry.baryshkov@linaro.org>
Date: Mon, 5 Sep 2022 13:45:42 +0300
From: Dmitry Baryshkov <dmitry.baryshkov@...aro.org>
To: Andy Whitcroft <apw@...onical.com>, Joe Perches <joe@...ches.com>,
Dwaipayan Ray <dwaipayanray1@...il.com>,
Lukas Bulwahn <lukas.bulwahn@...il.com>
Cc: linux-kernel@...r.kernel.org, Rob Clark <robdclark@...il.com>
Subject: [PATCH] checkpatch: move duplicate sign off to separate warning type
Some maintainers prefer to allow duplicate signatures if that provides
additional details about the patch flow. E.g. if the original patch
author pulls the patch from the patchwork into the kernel branch, this
can result in duplicate SOB tags from him, however this reflects the
patch flow (one SOB for being the author, one SOB for pulling the patch,
adding (and maybe fixing) tags and pushing the patch further.
To facilitate easily handling this kind of warnings, separate duplicate
SOBs into the separate warning class ('DUPLICATE_SIGN_OFF').
Cc: Rob Clark <robdclark@...il.com>
Signed-off-by: Dmitry Baryshkov <dmitry.baryshkov@...aro.org>
---
scripts/checkpatch.pl | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/scripts/checkpatch.pl b/scripts/checkpatch.pl
index 79e759aac543..f95d4ac19901 100755
--- a/scripts/checkpatch.pl
+++ b/scripts/checkpatch.pl
@@ -3115,7 +3115,7 @@ sub process {
$sig_nospace =~ s/\s//g;
$sig_nospace = lc($sig_nospace);
if (defined $signatures{$sig_nospace}) {
- WARN("BAD_SIGN_OFF",
+ WARN("DUPLICATE_SIGN_OFF",
"Duplicate signature\n" . $herecurr);
} else {
$signatures{$sig_nospace} = 1;
--
2.35.1
Powered by blists - more mailing lists