From: Hemant Agrawal <hemant.agrawal@nxp.com>
To: Neil Horman <nhorman@tuxdriver.com>, <dev@dpdk.org>
Cc: Thomas Monjalon <thomas@monjalon.net>
Subject: Re: [dpdk-dev] [PATCH] relicense various bits of the dpdk
Date: Tue, 5 Dec 2017 16:14:27 +0530 [thread overview]
Message-ID: <fe448390-ae42-a3b4-ae91-e791d8ea750e@nxp.com> (raw)
In-Reply-To: <20171204155557.31915-1-nhorman@tuxdriver.com>
On 12/4/2017 9:25 PM, Neil Horman wrote:
> Received a note the other day from the Linux Foundation governance board
> for DPDK indicating that several files I have copyright on need to be
> relicensed to be compliant with the DPDK licensing guidelines. I have
> some concerns with some parts of the request, but am not opposed to
> other parts. So, for those pieces that we are in consensus on, I'm
> proposing that we change their license from BSD 2 clause to 3 clause.
> I'm also updating the files to use the SPDX licensing scheme
>
> Signed-off-by: Neil Horman <nhorman@tuxdriver.com>
> CC: Hemant Agrawal <hemant.agrawal@nxp.com>
> CC: Thomas Monjalon <thomas@monjalon.net>
> ---
> devtools/validate-abi.sh | 32 ++++----------------------------
> lib/librte_compat/rte_compat.h | 24 +-----------------------
> 2 files changed, 5 insertions(+), 51 deletions(-)
Acked-by: Hemant Agrawal <hemant.agrawal@nxp.com>
next prev parent reply other threads:[~2017-12-05 10:44 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-04 15:55 Neil Horman
2017-12-05 10:44 ` Hemant Agrawal [this message]
2018-01-05 10:53 ` Thomas Monjalon
2018-02-01 0:31 ` Thomas Monjalon
2018-02-01 1:49 ` Neil Horman
2018-02-01 12:19 ` [dpdk-dev] [PATCH v2] " Neil Horman
2018-02-01 12:49 ` Hemant Agrawal
2018-02-06 22:16 ` 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=fe448390-ae42-a3b4-ae91-e791d8ea750e@nxp.com \
--to=hemant.agrawal@nxp.com \
--cc=dev@dpdk.org \
--cc=nhorman@tuxdriver.com \
--cc=thomas@monjalon.net \
/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).