From: Stephen Hemminger <stephen@networkplumber.org>
To: dev@dpdk.org
Cc: Stephen Hemminger <stephen@networkplumber.org>
Subject: [RFC] checkpatch: don't complain about SPDX tag format
Date: Tue, 17 Apr 2018 14:49:19 -0700 [thread overview]
Message-ID: <20180417214919.8246-1-stephen@networkplumber.org> (raw)
Since DPDK developers have decided to use a different tag format
than the kernel developers, ignore warnings about SPDX tags.
Signed-off-by: Stephen Hemminger <stephen@networkplumber.org>
---
IMHO would have been better to use the kernel SPDX style and
keep the check but that appears to be a minority opinion.
devtools/checkpatches.sh | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/devtools/checkpatches.sh b/devtools/checkpatches.sh
index 7676a6b50141..b438fbcd6737 100755
--- a/devtools/checkpatches.sh
+++ b/devtools/checkpatches.sh
@@ -42,7 +42,7 @@ options="--no-tree"
options="$options --max-line-length=$length"
options="$options --show-types"
options="$options --ignore=LINUX_VERSION_CODE,\
-FILE_PATH_CHANGES,MAINTAINERS_STYLE,\
+FILE_PATH_CHANGES,MAINTAINERS_STYLE,SPDX_LICENSE_TAG,\
VOLATILE,PREFER_PACKED,PREFER_ALIGNED,PREFER_PRINTF,\
PREFER_KERNEL_TYPES,BIT_MACRO,CONST_STRUCT,\
SPLIT_STRING,LONG_LINE_STRING,\
--
2.17.0
next reply other threads:[~2018-04-17 21:49 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-17 21:49 Stephen Hemminger [this message]
2018-04-17 22:06 ` [RFC] checkpatch: don't complain about SPDX tag format Thomas Monjalon
2018-04-17 22:11 ` Scott Branden
2018-04-17 22:19 ` Thomas Monjalon
2018-04-18 8:56 ` Bruce Richardson
2018-04-18 10:49 ` Kuusisaari, Juhamatti
2018-04-18 13:28 ` Bruce Richardson
2018-04-18 13:50 ` Thomas Monjalon
2018-04-18 15:25 ` Wiles, Keith
2018-04-19 12:42 ` Hemant Agrawal
2018-06-08 19:41 ` Thomas Monjalon
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=20180417214919.8246-1-stephen@networkplumber.org \
--to=stephen@networkplumber.org \
--cc=dev@dpdk.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.