DPDK patches and discussions
 help / color / mirror / Atom feed
From: Stephen Hemminger <stephen@networkplumber.org>
To: dev@dpdk.org
Cc: Stephen Hemminger <stephen@networkplumber.org>
Subject: [dpdk-dev] [PATCH 2/5] devtools: add license tag to cocci.sh
Date: Wed,  4 Dec 2019 07:55:16 -0800	[thread overview]
Message-ID: <20191204155519.7295-3-stephen@networkplumber.org> (raw)
In-Reply-To: <20191204155519.7295-1-stephen@networkplumber.org>

This file still had original BSD boilerplate text.
Replace it with SPDX tag.

Signed-off-by: Stephen Hemminger <stephen@networkplumber.org>
---
 devtools/cocci.sh | 30 +-----------------------------
 1 file changed, 1 insertion(+), 29 deletions(-)

diff --git a/devtools/cocci.sh b/devtools/cocci.sh
index 8b17a8cebac3..77b7447cdfcd 100755
--- a/devtools/cocci.sh
+++ b/devtools/cocci.sh
@@ -1,34 +1,6 @@
 #! /bin/sh
-
-# BSD LICENSE
-#
+# SPDX-License-Identifier: BSD-3-Clause
 # Copyright 2015 EZchip Semiconductor Ltd.
-#
-# 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 EZchip Semiconductor 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.
 
 # Apply coccinelle transforms.
 
-- 
2.20.1


  parent reply	other threads:[~2019-12-04 15:55 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-12-04 15:55 [dpdk-dev] [PATCH 0/5] SPDX leftovers Stephen Hemminger
2019-12-04 15:55 ` [dpdk-dev] [PATCH 1/5] app/test: add SPDX tag to timer test Stephen Hemminger
2019-12-04 15:55 ` Stephen Hemminger [this message]
2020-01-27 10:52   ` [dpdk-dev] [PATCH 2/5] devtools: add license tag to cocci.sh Mcnamara, John
2019-12-04 15:55 ` [dpdk-dev] [PATCH 3/5] devtools: add SPDX tag to load-devel-config Stephen Hemminger
2020-02-22 14:16   ` Thomas Monjalon
2019-12-04 15:55 ` [dpdk-dev] [PATCH 4/5] examples/ipsecgw: add SPDX license tag Stephen Hemminger
2019-12-05 20:42   ` Ananyev, Konstantin
2019-12-04 15:55 ` [dpdk-dev] [PATCH 5/5] examples/performance-thread: add mising SPDX tag Stephen Hemminger

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=20191204155519.7295-3-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 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).