From: Tetsuya Mukawa <mtetsuyah@gmail.com>
To: Stephen Hemminger <stephen@networkplumber.org>
Cc: dev@dpdk.org, Takanari Hayama <taki@igel.co.jp>
Subject: Re: [dpdk-dev] [PATCH] net/null: replace BSD text with SPDX id
Date: Mon, 26 Aug 2019 10:07:03 +0900 [thread overview]
Message-ID: <CANbst6E8iwsn4ryobt4=XL9nOZdDwCNVVeFYZNLKGvuLRdeXxg@mail.gmail.com> (raw)
In-Reply-To: <20190816204321.3487-1-stephen@networkplumber.org>
2019年8月17日(土) 5:43 Stephen Hemminger <stephen@networkplumber.org>:
>
> Replace the boilerplate BSD license text with the equivalent
> SPDX license id.
>
> Signed-off-by: Stephen Hemminger <stephen@networkplumber.org>
> Acked-by: Tetsuya Mukawa <mtetsuyah@gmail.com>
> ---
> drivers/net/null/rte_eth_null.c | 34 +++------------------------------
> 1 file changed, 3 insertions(+), 31 deletions(-)
>
> diff --git a/drivers/net/null/rte_eth_null.c b/drivers/net/null/rte_eth_null.c
> index b2c92ab72aec..0c60d241ac19 100644
> --- a/drivers/net/null/rte_eth_null.c
> +++ b/drivers/net/null/rte_eth_null.c
> @@ -1,34 +1,6 @@
> -/*-
> - * BSD LICENSE
> - *
> - * Copyright (C) IGEL Co.,Ltd.
> - * 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 IGEL Co.,Ltd. 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) IGEL Co.,Ltd.
> + * All rights reserved.
> */
>
> #include <rte_mbuf.h>
> --
> 2.20.1
>
I've already moved to other company.
I'm not sure you need 'acked' from me or IGEL.
Anyway, I added acked below, also Hayama-san will send 'acked' too.
Acked-by: Tetsuya Mukawa <mtetsuyah@gmail.com>
Thanks,
Tetsuya
next prev parent reply other threads:[~2019-08-26 1:07 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-16 20:43 Stephen Hemminger
2019-08-26 1:07 ` Tetsuya Mukawa [this message]
2019-08-26 3:15 ` Takanari Hayama
2019-08-26 12: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='CANbst6E8iwsn4ryobt4=XL9nOZdDwCNVVeFYZNLKGvuLRdeXxg@mail.gmail.com' \
--to=mtetsuyah@gmail.com \
--cc=dev@dpdk.org \
--cc=stephen@networkplumber.org \
--cc=taki@igel.co.jp \
/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).