From: Hemant Agrawal <hemant.agrawal@nxp.com>
To: Jan Viktorin <viktorin@rehivetech.com>, dev@dpdk.org
Cc: jerin.jacob@caviumnetworks.com, Thomas Monjalon <thomas@monjalon.net>
Subject: Re: [dpdk-dev] [PATCH 1/6] mk: use SPDX tag for RehiveTech copyright files
Date: Tue, 10 Apr 2018 09:40:32 +0530 [thread overview]
Message-ID: <5ba9a166-1ac7-320d-a549-b8379aa5acdc@nxp.com> (raw)
In-Reply-To: <20180409221558.3009-2-viktorin@rehivetech.com>
On 4/10/2018 3:45 AM, Jan Viktorin wrote:
> Replace the BSD license header with the SPDX tag for files
> with only an RehiveTech copyright on them.
>
> Signed-off-by: Jan Viktorin <viktorin@rehivetech.com>
> ---
> mk/arch/arm/rte.vars.mk | 32 ++------------------------------
> mk/machine/armv7a/rte.vars.mk | 31 ++-----------------------------
> 2 files changed, 4 insertions(+), 59 deletions(-)
>
> diff --git a/mk/arch/arm/rte.vars.mk b/mk/arch/arm/rte.vars.mk
> index 2f8cf7cb9..27b114761 100644
> --- a/mk/arch/arm/rte.vars.mk
> +++ b/mk/arch/arm/rte.vars.mk
> @@ -1,33 +1,5 @@
> -# BSD LICENSE
> -#
> -# 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 RehiveTech 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) 2015 RehiveTech. All rights reserved.
Acked-by: Hemant Agrawal <hemant.agrawal@nxp.com>
<snip>...
next prev parent reply other threads:[~2018-04-10 4:10 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 [this message]
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 ` [dpdk-dev] [PATCH 6/6] lib: use SPDX tag for Cavium & " Jan Viktorin
2018-04-10 0:43 ` 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=5ba9a166-1ac7-320d-a549-b8379aa5acdc@nxp.com \
--to=hemant.agrawal@nxp.com \
--cc=dev@dpdk.org \
--cc=jerin.jacob@caviumnetworks.com \
--cc=thomas@monjalon.net \
--cc=viktorin@rehivetech.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).