DPDK patches and discussions
 help / color / mirror / Atom feed
From: "O'Driscoll, Tim" <tim.odriscoll@intel.com>
To: "Sekhar, Ashwin" <Ashwin.Sekhar@cavium.com>,
	"thomas@monjalon.net" <thomas@monjalon.net>
Cc: "Mcnamara, John" <john.mcnamara@intel.com>,
	"govboard@dpdk.org" <govboard@dpdk.org>,
	"Jacob,  Jerin" <Jerin.JacobKollanukkaran@cavium.com>,
	"techboard@dpdk.org" <techboard@dpdk.org>,
	"dev@dpdk.org" <dev@dpdk.org>,
	"jianbo.liu@linaro.org" <jianbo.liu@linaro.org>
Subject: Re: [dpdk-dev] [PATCH v3 2/2] examples/performance-thread: add arm64 support
Date: Tue, 4 Jul 2017 14:02:59 +0000	[thread overview]
Message-ID: <26FA93C7ED1EAA44AB77D62FBE1D27BA9B0212A8@IRSMSX108.ger.corp.intel.com> (raw)
In-Reply-To: <1499153843.9925.5.camel@caviumnetworks.com>

> From: Sekhar, Ashwin [mailto:Ashwin.Sekhar@cavium.com]
> 
> This license is already there in many files in examples/performance-
> thread directory.
> 
> There are two cases in my patch.
> 
> 1.
> I moved some code from examples/performance-thread/common/lthread.c to
> examples/performance-thread/common/arch/x86/stack.h.
> lthread.c already has the below kind of license. So I think there is no
> issue retaining the same in stack.h also.

That sounds reasonable to me. IANAL, but I don't understand the license in the performance-thread example. It uses BSD 3-clause but references some code that was originally released under BSD 2-clause. It doesn't state that it's dual-licensed, and as far as I know, wasn't re-licensed by the original copyright holder. Anyway, that's an existing problem and not something created by your changes. We'll need to look into it and probably update the IP section of the Project Charter to reflect this.

> 
> 2.
> I added the following files.
> examples/performance-thread/common/arch/arm64/ctx.c
> examples/performance-thread/common/arch/arm64/ctx.h
> examples/performance-thread/common/arch/arm64/stack.h
> 
> These are actually written by me and not taken from the github link.
> By mistake I copied the license entirely :)
> 
> For these files, I shall remove it and re-post a v3.
> 
> Thanks
> Ashwin
> 
> 
> On Mon, 2017-07-03 at 21:21 +0000, O'Driscoll, Tim wrote:
> > >
> > > From: dev [mailto:dev-bounces@dpdk.org] On Behalf Of Thomas
> > > Monjalon
> > >
> > > There can be a licensing issue here.
> > > We may need advice from the Governing Board and the Technical
> > > Board.
> > That's correct. This uses a 2-clause BSD license, but the
> > Intellectual Property Policy section in the Project Charter (http://d
> > pdk.org/about/charter#ip) specifies 3-clause BSD. If you really need
> > to use a new license, then you'll need to make a request to the
> > Governing Board as specified in clause 6.c in the charter.
> >
> > >
> > >
> > > 18/05/2017 12:21, Ashwin Sekhar T K:
> > > >
> > > > +/*
> > > > + * https://github.com/halayli/lthread which carries the
> > > > following
> > > license.
> > > >
> > > > + *
> > > > + * Copyright (C) 2012, Hasan Alayli <halayli@gmail.com>
> > > > + *
> > > > + * Redistribution and use in source and binary forms, with or
> > > > without
> > > > + * modification, are permitted provided that the following
> > > > conditions
> > > > + * are met:
> > > > + * 1. Redistributions of source code must retain the above
> > > > copyright
> > > > + *    notice, this list of conditions and the following
> > > > disclaimer.
> > > > + * 2. Redistributions in binary form must reproduce the above
> > > copyright
> > > >
> > > > + *    notice, this list of conditions and the following
> > > > disclaimer in
> > > the
> > > >
> > > > + *    documentation and/or other materials provided with the
> > > distribution.
> > > >
> > > > + *
> > > > + * THIS SOFTWARE IS PROVIDED BY AUTHOR AND CONTRIBUTORS ``AS
> > > > IS'' AND
> > > > + * ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED
> > > > TO,
> > > THE
> > > >
> > > > + * IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A
> > > > PARTICULAR
> > > PURPOSE
> > > >
> > > > + * ARE DISCLAIMED.  IN NO EVENT SHALL AUTHOR OR CONTRIBUTORS BE
> > > LIABLE
> > > >
> > > > + * FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR
> > > CONSEQUENTIAL
> > > >
> > > > + * DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF
> > > > SUBSTITUTE
> > > GOODS
> > > >
> > > > + * OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS
> > > INTERRUPTION)
> > > >
> > > > + * HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN
> > > CONTRACT, STRICT
> > > >
> > > > + * LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE)
> > > > ARISING IN
> > > ANY WAY
> > > >
> > > > + * OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
> > > POSSIBILITY OF
> > > >
> > > > + * SUCH DAMAGE.
> > > > + */

  reply	other threads:[~2017-07-04 14:03 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-05-17 18:19 [dpdk-dev] [PATCH] " Ashwin Sekhar T K
2017-05-17 18:44 ` Jerin Jacob
2017-05-18  6:35   ` Jianbo Liu
2017-05-18  7:38     ` Sekhar, Ashwin
2017-05-18  7:34 ` [dpdk-dev] [PATCH v2 0/2] " Ashwin Sekhar T K
2017-05-18  7:34   ` [dpdk-dev] [PATCH v2 1/2] examples/performance-thread: reorganise arch dependent code Ashwin Sekhar T K
2017-05-18  7:34   ` [dpdk-dev] [PATCH v2 2/2] examples/performance-thread: add arm64 support Ashwin Sekhar T K
2017-05-18  8:55     ` Jerin Jacob
2017-05-18  9:00       ` Sekhar, Ashwin
2017-05-18 10:21 ` [dpdk-dev] [PATCH v3 0/2] " Ashwin Sekhar T K
2017-05-18 10:21   ` [dpdk-dev] [PATCH v3 1/2] examples/performance-thread: reorganise arch dependent code Ashwin Sekhar T K
2017-05-18 10:21   ` [dpdk-dev] [PATCH v3 2/2] examples/performance-thread: add arm64 support Ashwin Sekhar T K
2017-07-03 20:57     ` Thomas Monjalon
2017-07-03 21:21       ` O'Driscoll, Tim
2017-07-04  7:37         ` Sekhar, Ashwin
2017-07-04 14:02           ` O'Driscoll, Tim [this message]
2017-07-04  8:05 ` [dpdk-dev] [PATCH v4 0/2] " Ashwin Sekhar T K
2017-07-04  8:05   ` [dpdk-dev] [PATCH v4 1/2] examples/performance-thread: reorganise arch dependent code Ashwin Sekhar T K
2017-07-04  8:05   ` [dpdk-dev] [PATCH v4 2/2] examples/performance-thread: add arm64 support Ashwin Sekhar T K
2017-07-04  8:22 ` [dpdk-dev] [PATCH v5 0/2] " Ashwin Sekhar T K
2017-07-04  8:22   ` [dpdk-dev] [PATCH v5 1/2] examples/performance-thread: reorganise arch dependent code Ashwin Sekhar T K
2017-07-04  8:22   ` [dpdk-dev] [PATCH v5 2/2] examples/performance-thread: add arm64 support Ashwin Sekhar T K
2017-07-04 13:20   ` [dpdk-dev] [PATCH v5 0/2] " 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=26FA93C7ED1EAA44AB77D62FBE1D27BA9B0212A8@IRSMSX108.ger.corp.intel.com \
    --to=tim.odriscoll@intel.com \
    --cc=Ashwin.Sekhar@cavium.com \
    --cc=Jerin.JacobKollanukkaran@cavium.com \
    --cc=dev@dpdk.org \
    --cc=govboard@dpdk.org \
    --cc=jianbo.liu@linaro.org \
    --cc=john.mcnamara@intel.com \
    --cc=techboard@dpdk.org \
    --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).