From: Neil Horman <nhorman@tuxdriver.com>
To: Hemant Agrawal <hemant.agrawal@nxp.com>
Cc: dev@dpdk.org, techboard@dpdk.org
Subject: Re: [dpdk-dev] [PATCH] pmdinfogen: add SPDX license tag
Date: Tue, 3 Sep 2019 08:15:41 -0400 [thread overview]
Message-ID: <20190903121541.GA30429@hmswarspite.think-freely.org> (raw)
In-Reply-To: <20190903072435.2859-1-hemant.agrawal@nxp.com>
On Tue, Sep 03, 2019 at 12:54:35PM +0530, Hemant Agrawal wrote:
> This patch adds SPDX license tag to pmdinfogen files.
>
> These files are originally drived from kernel.
> They are being used as binary tool to support internal
> build.
>
> This patch requires license exception approval from
> DPDK Technical Board and Governing Board.
>
> Signed-off-by: Hemant Agrawal <hemant.agrawal@nxp.com>
> ---
> buildtools/pmdinfogen/pmdinfogen.c | 7 ++-----
> buildtools/pmdinfogen/pmdinfogen.h | 8 ++------
> license/exceptions.txt | 4 +++-
> 3 files changed, 7 insertions(+), 12 deletions(-)
>
> diff --git a/buildtools/pmdinfogen/pmdinfogen.c b/buildtools/pmdinfogen/pmdinfogen.c
> index dc0b6d5ff..a68d1ea99 100644
> --- a/buildtools/pmdinfogen/pmdinfogen.c
> +++ b/buildtools/pmdinfogen/pmdinfogen.c
> @@ -1,11 +1,8 @@
> -/* Postprocess pmd object files to export hw support
> +/* SPDX-License-Identifier: GPL-2.0
> + * Postprocess pmd object files to export hw support
> *
> * Copyright 2016 Neil Horman <nhorman@tuxdriver.com>
> * Based in part on modpost.c from the linux kernel
> - *
> - * This software may be used and distributed according to the terms
> - * of the GNU General Public License V2, incorporated herein by reference.
> - *
> */
>
> #include <stdio.h>
> diff --git a/buildtools/pmdinfogen/pmdinfogen.h b/buildtools/pmdinfogen/pmdinfogen.h
> index c8a9e2136..e6ba54535 100644
> --- a/buildtools/pmdinfogen/pmdinfogen.h
> +++ b/buildtools/pmdinfogen/pmdinfogen.h
> @@ -1,12 +1,8 @@
> -
> -/* Postprocess pmd object files to export hw support
> +/* SPDX-License-Identifier: GPL-2.0
> + * Postprocess pmd object files to export hw support
> *
> * Copyright 2016 Neil Horman <nhorman@tuxdriver.com>
> * Based in part on modpost.c from the linux kernel
> - *
> - * This software may be used and distributed according to the terms
> - * of the GNU General Public License V2, incorporated herein by reference.
> - *
> */
>
> #include <stdio.h>
> diff --git a/license/exceptions.txt b/license/exceptions.txt
> index f1cfa462f..9443dfc63 100644
> --- a/license/exceptions.txt
> +++ b/license/exceptions.txt
> @@ -12,7 +12,9 @@ Note that following licenses are not exceptions:-
> -----------------------------------------------------------------
> SPDX Identifier TB Approval Date GB Approval Date File name
> -----------------------------------------------------------------
> -1.
> +1.GPL-2.0 TBD TBD buildtools/pmdinfogen/pmdinfogen.c
> +1.GPL-2.0 TBD TBD buildtools/pmdinfogen/pmdinfogen.h
> +
>
> -----------------------------------------------------------------
>
> --
> 2.17.1
>
>
Acked-by: Neil Horman <nhorman@tuxdriver.com>
next prev parent reply other threads:[~2019-09-03 13:13 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-03 7:24 Hemant Agrawal
2019-09-03 12:15 ` Neil Horman [this message]
2019-12-31 1:05 ` 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=20190903121541.GA30429@hmswarspite.think-freely.org \
--to=nhorman@tuxdriver.com \
--cc=dev@dpdk.org \
--cc=hemant.agrawal@nxp.com \
--cc=techboard@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).