DPDK patches and discussions
 help / color / mirror / Atom feed
From: Pavan Nikhilesh Bhagavatula <pbhagavatula@caviumnetworks.com>
To: "hemant.agrawal@nxp.com" <hemant.agrawal@nxp.com>,
	konstantin.ananyev@intel.com, jerin.jacob@caviumnetworks.com,
	Jan Blunck <jblunck@infradead.org>,
	Stephen Hemminger <stephen@networkplumber.org>,
	Thomas Monjalon <thomas@monjalon.net>,
	"techboard@dpdk.org" <techboard@dpdk.org>
Cc: dev@dpdk.org
Subject: [dpdk-dev]  DPDK techboard minutes of September 15]
Date: Wed, 4 Oct 2017 14:45:46 +0530	[thread overview]
Message-ID: <20171004091545.GA20260@PBHAGAVATULA-LT> (raw)

On Wed, Sep 20, 2017 at 09:36:48PM +0000, Ananyev, Konstantin wrote:

Hi everyone,

As per the last techboard meeting's conclusion,

<snip>
>
> 3) Request for feedback regarding the new license requirement for the optimized version of 64bit division code from libdivide.
> It was pointed out that current 32-bit version is not BSD-licensed either:
> http://dpdk.org/browse/dpdk/tree/lib/librte_sched/rte_reciprocal.h
> TB recommendations:
> a) request LF legals to audit current lib/librte_sched/rte_reciprocal.h
> b) ask author of the patch for 64-bit version to:
>     - try to find BSD licensed implementation of the same algorithm
>     - contact the authors of the original code and ask their permission for re-licensing in BSD

I have contacted the author and got the following response

-------------------------------------------------------------------------------
"libdivide is made available under the zlib license, which is very permissive
and compatible with BSD licenses. libdivide may be freely used in BSD-licensed
software, or also GPL or commercial software.

You do not have to add any copyright notices if you use libdivide in your
binaries. If you simply add libdivide.h to your sources and use it, you are
complying with the license.

It is my hope with libdivide that anyone can use it for anything.
The license is only so that nobody else claims to be the original author."


"It’s fine to modify libdivide to remove pieces you don’t use, or just copy
and paste the parts you do use. However it’s not reasonable to ask me to
contribute libdivide "without the licensing part;” in fact I cannot do so
because libdivide has more than one contributor.

The good news is that using libdivide under its license is very easy!
You only have to include the 14 line license text (under "ZLib license”).
The simplest way is with a source code comment in the file itself - I see you
have several other acknowledgements in rte_reciprocal.h, so that seems like a
natural place. A separate acknowledgements file is also fine if you prefer.

I hope that explains things and thanks for understanding,
_fish"
-------------------------------------------------------------------------------

The authors concern is contributing it to BSD licence will be a weak link
to the original author credits.

>
<snip>
>
> Thanks,
> Konstantin

Thanks,
Pavan

             reply	other threads:[~2017-10-04  9:16 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-10-04  9:15 Pavan Nikhilesh Bhagavatula [this message]
2017-10-04 10:04 ` Hemant Agrawal

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=20171004091545.GA20260@PBHAGAVATULA-LT \
    --to=pbhagavatula@caviumnetworks.com \
    --cc=dev@dpdk.org \
    --cc=hemant.agrawal@nxp.com \
    --cc=jblunck@infradead.org \
    --cc=jerin.jacob@caviumnetworks.com \
    --cc=konstantin.ananyev@intel.com \
    --cc=stephen@networkplumber.org \
    --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).