From: Jerin Jacob <jerin.jacob@caviumnetworks.com>
To: dev@dpdk.org
Cc: thomas@monjalon.net, hemant.agrawal@nxp.com,
Jerin Jacob <jerin.jacob@caviumnetworks.com>
Subject: [dpdk-dev] [PATCH v2 9/9] tools: use SPDX tag for Cavium copyright files
Date: Mon, 8 Jan 2018 10:55:20 +0530 [thread overview]
Message-ID: <20180108052520.8331-9-jerin.jacob@caviumnetworks.com> (raw)
In-Reply-To: <20180108052520.8331-1-jerin.jacob@caviumnetworks.com>
Signed-off-by: Jerin Jacob <jerin.jacob@caviumnetworks.com>
---
devtools/build-tags.sh | 34 +++++-----------------------------
1 file changed, 5 insertions(+), 29 deletions(-)
diff --git a/devtools/build-tags.sh b/devtools/build-tags.sh
index 942da2bae..78001f048 100755
--- a/devtools/build-tags.sh
+++ b/devtools/build-tags.sh
@@ -1,35 +1,11 @@
#!/bin/sh -e
+# SPDX-License-Identifier: BSD-3-Clause
+# Copyright(c) 2017 Cavium, Inc
+#
+
+#
# Generate tags or gtags or cscope or etags files
#
-# BSD LICENSE
-#
-# Copyright 2017 Cavium, Inc
-#
-# Redistribution and use in source and binary forms, with or without
-# modification, are permitted provided that the following conditions
-# are met:
-#
-# * Redistributions of source code must retain the above copyright
-# notice, this list of conditions and the following disclaimer.
-# * Redistributions in binary form must reproduce the above copyright
-# notice, this list of conditions and the following disclaimer in
-# the documentation and/or other materials provided with the
-# distribution.
-# * Neither the name of Cavium, Inc nor the names of its
-# contributors may be used to endorse or promote products derived
-# from this software without specific prior written permission.
-#
-# THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS
-# "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT
-# LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR
-# A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT
-# OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL,
-# SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT
-# LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE,
-# DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY
-# THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT
-# (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE
-# OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
verbose=false
linux=true
--
2.15.1
next prev parent reply other threads:[~2018-01-08 5:26 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-06 12:19 [dpdk-dev] [PATCH 1/9] test: " Jerin Jacob
2018-01-06 12:19 ` [dpdk-dev] [PATCH 2/9] mk: " Jerin Jacob
2018-01-06 12:19 ` [dpdk-dev] [PATCH 3/9] lib: " Jerin Jacob
2018-01-06 12:20 ` [dpdk-dev] [PATCH 4/9] examples: " Jerin Jacob
2018-01-06 12:20 ` [dpdk-dev] [PATCH 5/9] drivers: " Jerin Jacob
2018-01-06 12:20 ` [dpdk-dev] [PATCH 6/9] app: " Jerin Jacob
2018-01-06 12:20 ` [dpdk-dev] [PATCH 7/9] doc: " Jerin Jacob
2018-01-06 12:20 ` [dpdk-dev] [PATCH 8/9] config: " Jerin Jacob
2018-01-06 12:20 ` [dpdk-dev] [PATCH 9/9] tools: " Jerin Jacob
2018-01-07 8:54 ` Hemant Agrawal
2018-01-08 5:16 ` Jerin Jacob
2018-01-08 5:25 ` [dpdk-dev] [PATCH v2 1/9] test: " Jerin Jacob
2018-01-08 5:25 ` [dpdk-dev] [PATCH v2 2/9] mk: " Jerin Jacob
2018-01-08 5:25 ` [dpdk-dev] [PATCH v2 3/9] lib: " Jerin Jacob
2018-01-08 5:25 ` [dpdk-dev] [PATCH v2 4/9] examples: " Jerin Jacob
2018-01-08 5:25 ` [dpdk-dev] [PATCH v2 5/9] drivers: " Jerin Jacob
2018-01-08 5:25 ` [dpdk-dev] [PATCH v2 6/9] app: " Jerin Jacob
2018-01-08 5:25 ` [dpdk-dev] [PATCH v2 7/9] doc: " Jerin Jacob
2018-01-08 5:25 ` [dpdk-dev] [PATCH v2 8/9] config: " Jerin Jacob
2018-01-08 5:25 ` Jerin Jacob [this message]
2018-01-09 7:56 ` [dpdk-dev] [PATCH v2 1/9] test: " Hemant Agrawal
2018-01-09 15:20 ` 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=20180108052520.8331-9-jerin.jacob@caviumnetworks.com \
--to=jerin.jacob@caviumnetworks.com \
--cc=dev@dpdk.org \
--cc=hemant.agrawal@nxp.com \
--cc=thomas@monjalon.net \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).