DPDK patches and discussions
 help / color / mirror / Atom feed
From: Hemant Agrawal <hemant.agrawal@nxp.com>
To: dev@dpdk.org
Cc: Hemant Agrawal <hemant.agrawal@nxp.com>
Subject: [dpdk-dev] [PATCH v2] pmdinfogen: add SPDX license tag
Date: Fri, 27 Sep 2019 14:09:56 +0530	[thread overview]
Message-ID: <20190927083956.30311-1-hemant.agrawal@nxp.com> (raw)

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>
Acked-by: Neil Horman <nhorman@tuxdriver.com>
---
 buildtools/pmdinfogen/pmdinfogen.c | 7 ++-----
 buildtools/pmdinfogen/pmdinfogen.h | 8 ++------
 license/exceptions.txt             | 4 ++--
 3 files changed, 6 insertions(+), 13 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..1acd5733f 100644
--- a/license/exceptions.txt
+++ b/license/exceptions.txt
@@ -7,12 +7,12 @@ Note that following licenses are not exceptions:-
 	- BSD-3-Clause
 	- Dual BSD-3-Clause OR GPL-2.0
 	- Dual BSD-3-Clause OR LGPL-2.1
-	- GPL-2.0  (*Only for kernel code*)
+	- GPL-2.0  (*Only for kernel code and tools*)
 
 -----------------------------------------------------------------
 SPDX Identifier     TB Approval Date  GB Approval Date  File name
 -----------------------------------------------------------------
-1.
+1.GPL-2.0	25-Sep-2019 TBD		buildtools/pmdinfogen/pmdinfogen.*
 
 -----------------------------------------------------------------
 
-- 
2.17.1


             reply	other threads:[~2019-09-27  8:42 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-09-27  8:39 Hemant Agrawal [this message]
2020-02-22 12:25 ` 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=20190927083956.30311-1-hemant.agrawal@nxp.com \
    --to=hemant.agrawal@nxp.com \
    --cc=dev@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).