From: Jan Viktorin <viktorin@rehivetech.com>
To: dev@dpdk.org
Cc: jerin.jacob@caviumnetworks.com,
Thomas Monjalon <thomas@monjalon.net>,
Hemant Agrawal <hemant.agrawal@nxp.com>,
Jan Viktorin <viktorin@rehivetech.com>
Subject: [dpdk-dev] [PATCH 6/6] lib: use SPDX tag for Cavium & RehiveTech copyright files
Date: Tue, 10 Apr 2018 00:15:58 +0200 [thread overview]
Message-ID: <20180409221558.3009-7-viktorin@rehivetech.com> (raw)
In-Reply-To: <20180409221558.3009-1-viktorin@rehivetech.com>
Replace the BSD license header with the SPDX tag for files
with a RehiveTech and Cavium copyright on them.
Signed-off-by: Jan Viktorin <viktorin@rehivetech.com>
---
lib/librte_eal/common/arch/arm/rte_cpuflags.c | 34 +++------------------------
1 file changed, 3 insertions(+), 31 deletions(-)
diff --git a/lib/librte_eal/common/arch/arm/rte_cpuflags.c b/lib/librte_eal/common/arch/arm/rte_cpuflags.c
index 88f1cbe37..390a19a26 100644
--- a/lib/librte_eal/common/arch/arm/rte_cpuflags.c
+++ b/lib/librte_eal/common/arch/arm/rte_cpuflags.c
@@ -1,34 +1,6 @@
-/*
- * BSD LICENSE
- *
- * Copyright (C) Cavium, Inc. 2015.
- * Copyright(c) 2015 RehiveTech. 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 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.
+/* SPDX-License-Identifier: BSD-3-Clause
+ * Copyright (C) Cavium, Inc. 2015.
+ * Copyright(c) 2015 RehiveTech. All rights reserved.
*/
#include "rte_cpuflags.h"
--
2.16.2
next prev parent reply other threads:[~2018-04-09 22:16 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-09 22:15 [dpdk-dev] [PATCH 0/6] Use SPDX identifier of RehiveTech code Jan Viktorin
2018-04-09 22:15 ` [dpdk-dev] [PATCH 1/6] mk: use SPDX tag for RehiveTech copyright files Jan Viktorin
2018-04-10 4:10 ` Hemant Agrawal
2018-04-09 22:15 ` [dpdk-dev] [PATCH 2/6] lib: " Jan Viktorin
2018-04-10 4:15 ` Hemant Agrawal
2018-04-09 22:15 ` [dpdk-dev] [PATCH 3/6] drivers: " Jan Viktorin
2018-04-10 4:18 ` Hemant Agrawal
2018-04-09 22:15 ` [dpdk-dev] [PATCH 4/6] test: " Jan Viktorin
2018-04-10 4:17 ` Hemant Agrawal
2018-04-09 22:15 ` [dpdk-dev] [PATCH 5/6] config: " Jan Viktorin
2018-04-10 4:16 ` Hemant Agrawal
2018-04-09 22:15 ` Jan Viktorin [this message]
2018-04-10 0:43 ` [dpdk-dev] [PATCH 6/6] lib: use SPDX tag for Cavium & " Jerin Jacob
2018-04-10 23:02 ` [dpdk-dev] [PATCH 0/6] Use SPDX identifier of RehiveTech code 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=20180409221558.3009-7-viktorin@rehivetech.com \
--to=viktorin@rehivetech.com \
--cc=dev@dpdk.org \
--cc=hemant.agrawal@nxp.com \
--cc=jerin.jacob@caviumnetworks.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).