DPDK patches and discussions
 help / color / mirror / Atom feed
From: Thomas Monjalon <thomas@monjalon.net>
To: Neil Horman <nhorman@tuxdriver.com>
Cc: dev@dpdk.org, Hemant Agrawal <hemant.agrawal@nxp.com>
Subject: Re: [dpdk-dev] [PATCH v2] relicense various bits of the dpdk
Date: Tue, 06 Feb 2018 23:16:43 +0100	[thread overview]
Message-ID: <2341877.B6D55p2t3H@xps> (raw)
In-Reply-To: <74f19e7f-dc0f-ad3b-2a24-bb8260745a79@nxp.com>

01/02/2018 13:49, Hemant Agrawal:
> On 2/1/2018 5:49 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>
> 
> Acked-by: Hemant Agrawal <hemant.agrawal@nxp.com>

Applied, thanks

      reply	other threads:[~2018-02-06 22:16 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-12-04 15:55 [dpdk-dev] [PATCH] " Neil Horman
2017-12-05 10:44 ` Hemant Agrawal
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 [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=2341877.B6D55p2t3H@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).