DPDK patches and discussions
 help / color / mirror / Atom feed
From: Ferruh Yigit <ferruh.yigit@intel.com>
To: Shrikrishna Khare <skhare@vmware.com>,
	dev@dpdk.org, Hemant Agrawal <hemant.agrawal@nxp.com>
Cc: Thomas Monjalon <thomas@monjalon.net>
Subject: Re: [dpdk-dev] [PATCH] net/vmxnet3: convert to 3-Clause BSD License
Date: Thu, 7 Dec 2017 15:30:14 -0800	[thread overview]
Message-ID: <09219e45-90ff-75fb-d7f8-a29d8b3b7e18@intel.com> (raw)
In-Reply-To: <b7d9869c-2f98-502b-57de-685e7f18e8a2@intel.com>

On 12/7/2017 3:27 PM, Ferruh Yigit wrote:
> On 12/7/2017 1:59 PM, Shrikrishna Khare wrote:
>> On behalf of the DPDK Technical board, Hemant Agrawal observed that the
>> DPDK project's Intellectual Property Policy (http://dpdk.org/about/charter)
>> requires 3-Clause BSD license or an exception approval. However, two
>> vmxnet3 source files have 2-Clause BSD license.
>>
>> This patch modifies those licenses to 3-Clause BSD license.
>>
>> Reported-by: Hemant Agrawal <hemant.agrawal@nxp.com>
>> Acked-by: Cheryl Houser <chouser@vmware.com>
>> Acked-by: Bharat Mota <bmota@vmware.com>
>> Signed-off-by: Shrikrishna Khare <skhare@vmware.com>
> 
> Applied to dpdk-next-net/master, thanks.

Hi Hemant,

Just to clarify, we want license header update for all licenses including
existing BSD-3 ones, right? Not just for wrong/different license types.

Thanks,
ferruh

      reply	other threads:[~2017-12-07 23:30 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-12-07 21:59 Shrikrishna Khare
2017-12-07 23:27 ` Ferruh Yigit
2017-12-07 23:30   ` Ferruh Yigit [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=09219e45-90ff-75fb-d7f8-a29d8b3b7e18@intel.com \
    --to=ferruh.yigit@intel.com \
    --cc=dev@dpdk.org \
    --cc=hemant.agrawal@nxp.com \
    --cc=skhare@vmware.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).