DPDK patches and discussions
 help / color / mirror / Atom feed
From: Thomas Monjalon <thomas@monjalon.net>
To: Hemant Agrawal <hemant.agrawal@nxp.com>
Cc: dev@dpdk.org, Neil Horman <nhorman@tuxdriver.com>
Subject: Re: [dpdk-dev] [PATCH v2] pmdinfogen: add SPDX license tag
Date: Sat, 22 Feb 2020 13:25:55 +0100	[thread overview]
Message-ID: <2633978.Y6S9NjorxK@xps> (raw)
In-Reply-To: <20190927083956.30311-1-hemant.agrawal@nxp.com>

27/09/2019 10:39, Hemant Agrawal:
> 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>
> ---
> --- 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*)

GPL tools remain exceptions according to the Governing Board.
I will drop the addition of tools in "not exceptions" list.

>  -----------------------------------------------------------------
>  SPDX Identifier     TB Approval Date  GB Approval Date  File name
>  -----------------------------------------------------------------
> -1.
> +1.GPL-2.0	25-Sep-2019 TBD		buildtools/pmdinfogen/pmdinfogen.*
>  
>  -----------------------------------------------------------------

The pmdinfogen exception was approved by the Governing Board on 12/18/2019.

Applied with above changes, thanks.



      reply	other threads:[~2020-02-22 12:26 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-09-27  8:39 Hemant Agrawal
2020-02-22 12:25 ` Thomas Monjalon [this message]

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=2633978.Y6S9NjorxK@xps \
    --to=thomas@monjalon.net \
    --cc=dev@dpdk.org \
    --cc=hemant.agrawal@nxp.com \
    --cc=nhorman@tuxdriver.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).