DPDK patches and discussions
 help / color / mirror / Atom feed
From: Hemant Agrawal <hemant.agrawal@nxp.com>
To: dev@dpdk.org
Cc: jerin.jacob@caviumnetworks.com, Hemant Agrawal <hemant.agrawal@nxp.com>
Subject: [dpdk-dev] [PATCH] usertools: change to SPDX license identifier
Date: Mon,  9 Apr 2018 14:28:37 +0530	[thread overview]
Message-ID: <1523264319-26429-5-git-send-email-hemant.agrawal@nxp.com> (raw)
In-Reply-To: <1523264319-26429-1-git-send-email-hemant.agrawal@nxp.com>

Cc: jerin.jacob@caviumnetworks.com

Signed-off-by: Hemant Agrawal <hemant.agrawal@nxp.com>
---
 usertools/cpu_layout.py | 36 +++---------------------------------
 1 file changed, 3 insertions(+), 33 deletions(-)

diff --git a/usertools/cpu_layout.py b/usertools/cpu_layout.py
index d3c8eba..6f129b1 100755
--- a/usertools/cpu_layout.py
+++ b/usertools/cpu_layout.py
@@ -1,38 +1,8 @@
 #!/usr/bin/env python
+# SPDX-License-Identifier: BSD-3-Clause
+# Copyright(c) 2010-2014 Intel Corporation
+# Copyright(c) 2017 Cavium, Inc. All rights reserved.
 
-#
-#   BSD LICENSE
-#
-#   Copyright(c) 2010-2014 Intel Corporation. All rights reserved.
-#   Copyright(c) 2017 Cavium, Inc. All rights reserved.
-#   All rights reserved.
-#
-#   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 Intel Corporation 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.
-#
 from __future__ import print_function
 import sys
 try:
-- 
2.7.4

  parent reply	other threads:[~2018-04-09  9:00 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-04-09  8:58 [dpdk-dev] [PATCH] net/vmxnet3: change the SPDX tag style Hemant Agrawal
2018-04-09  8:58 ` [dpdk-dev] [PATCH] eal: add missing SPDX identifiers Hemant Agrawal
2018-05-25  8:20   ` Thomas Monjalon
2018-04-09  8:58 ` [dpdk-dev] [PATCH] test/crypto-perf: add missing SPDX identifier Hemant Agrawal
2018-04-17 15:08   ` De Lara Guarch, Pablo
2018-04-17 15:10   ` De Lara Guarch, Pablo
2018-04-09  8:58 ` [dpdk-dev] [PATCH] usertools: " Hemant Agrawal
2018-04-09 10:24   ` Neil Horman
2018-04-10 23:50     ` Thomas Monjalon
2018-04-09  8:58 ` Hemant Agrawal [this message]
2018-04-09  9:07   ` [dpdk-dev] [PATCH] usertools: change to SPDX license identifier Jerin Jacob
2018-04-10 23:50     ` Thomas Monjalon
2018-04-09  8:58 ` [dpdk-dev] [PATCH] kernel: add missing " Hemant Agrawal
2018-04-09  8:58 ` [dpdk-dev] [PATCH] pkg: change to " Hemant Agrawal
2018-05-25  8:22   ` Thomas Monjalon
2018-04-12 21:39 ` [dpdk-dev] [PATCH] net/vmxnet3: change the SPDX tag style Yong Wang
2018-04-17 17:44   ` Ferruh Yigit

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=1523264319-26429-5-git-send-email-hemant.agrawal@nxp.com \
    --to=hemant.agrawal@nxp.com \
    --cc=dev@dpdk.org \
    --cc=jerin.jacob@caviumnetworks.com \
    /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).