From: Stephen Hemminger <stephen@networkplumber.org>
To: "Dumitrescu, Cristian" <cristian.dumitrescu@intel.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH 0/3] sched: patches for 2.2
Date: Thu, 10 Mar 2016 10:44:13 -0800 [thread overview]
Message-ID: <CAOaVG14oFvwpv_UVWKdN_JM+QDsvDqx9dZL77BToC0qqU1S3sg@mail.gmail.com> (raw)
In-Reply-To: <3EB4FA525960D640B5BDFFD6A3D891264796C2D9@IRSMSX108.ger.corp.intel.com>
Why does this need to be reassigned to Intel. That is not how the DPDK
works.
Please leave the original copyright holders on the file.
On Thu, Mar 10, 2016 at 10:41 AM, Dumitrescu, Cristian <
cristian.dumitrescu@intel.com> wrote:
>
>
> > -----Original Message-----
> > From: Stephen Hemminger [mailto:stephen@networkplumber.org]
> > Sent: Tuesday, March 8, 2016 8:41 PM
> > To: Dumitrescu, Cristian <cristian.dumitrescu@intel.com>
> > Cc: Thomas Monjalon <thomas.monjalon@6wind.com>; dev@dpdk.org
> > Subject: Re: [dpdk-dev] [PATCH 0/3] sched: patches for 2.2
> >
> > On Tue, 8 Mar 2016 19:53:01 +0000
> > "Dumitrescu, Cristian" <cristian.dumitrescu@intel.com> wrote:
> >
> > >
> > >
> > > > -----Original Message-----
> > > > From: Stephen Hemminger [mailto:stephen@networkplumber.org]
> > > > Sent: Tuesday, March 8, 2016 4:33 PM
> > > > To: Dumitrescu, Cristian <cristian.dumitrescu@intel.com>
> > > > Cc: Thomas Monjalon <thomas.monjalon@6wind.com>; dev@dpdk.org
> > > > Subject: Re: [dpdk-dev] [PATCH 0/3] sched: patches for 2.2
> > > >
> > > > On Tue, 8 Mar 2016 07:49:20 +0000
> > > > "Dumitrescu, Cristian" <cristian.dumitrescu@intel.com> wrote:
> > > >
> > > > > Regarding Stephen's patches, I think there is a pending issue
> regarding
> > the
> > > > legal side of the Copyright, which is attributed to Intel, although
> > Stephen's
> > > > code is relicensed with BSD license by permission from the original
> code
> > > > author (which also submitted the code to Linux kernel under GPL).
> This
> > was
> > > > already flagged. This is a legal issue and I do not feel comfortable
> with
> > ack-ing
> > > > this patch until the legal resolution on this is crystal clear.
> > > >
> > > >
> > > > I got explicit permission from the author who holds the copyright to
> > relicense
> > > > it.
> > >
> > > Did you get explicit permission from the author who holds the
> copyright to
> > relicense it with BSD license that hands over the copyright to Intel?
> >
> > I got explicit permission to relicense as BSD.
> >
> >
> > I believe DPDK does not require copyright assignment, and this is a
> > standalone file.
> >
>
> Yes, I understand that you got permission from the author to relicense as
> BSD. What I am not sure of is whether it is OK to assign the copyright to
> Intel, maybe other people can comment on this as well.
>
> As explained above, rte_reciprocal.[hc] is a standalone algorithm that is
> independent of librte_sched code. It can useful to any piece of code
> requiring division on data plane side, including any DPDK library or app,
> even those not using librte_sched library, therefor it really does not
> belong to librte_sched. My proposal is:
> 1. Please submit patch series 1 with rte_reciprocal.[hc] as new files to
> be added to librte_eal/common.
> 2. Please submit patch series 2 containing just changes to librte_sched,
> which are small.
>
> Are you OK with this approach?
>
> Thanks,
> Cristian
>
>
> >
> > On Sat, Dec 20, 2014, at 01:24, Stephen Hemminger wrote:
> > > The kernel implementation of reciprocal divide is GPL licensed.
> > > Is there any chance of getting a BSD license version to allow using
> > > it in the DPDK?
> >
> > I absolutely don't have a problem to give my ack to make this
> > dual-license. Where do I need to sign? ;)
> >
> > Bye,
> > Hannes
> >
> > >> On Sat, Dec 20, 2014, at 01:24, Stephen Hemminger wrote:
> > >>> The kernel implementation of reciprocal divide is GPL licensed.
> > >>> Is there any chance of getting a BSD license version to allow using
> > >>> it in the DPDK?
> > >>
> > >> I absolutely don't have a problem to give my ack to make this
> > >> dual-license. Where do I need to sign? ;)
> >
> > I have absolutely no problem with that. Feel free to add my
> > Signed-off-by to your DPDK submission.
> >
> > Merry X-Mas & thanks for asking!
> >
> > Daniel
>
next prev parent reply other threads:[~2016-03-10 18:44 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-29 18:46 Stephen Hemminger
2015-11-29 18:46 ` [dpdk-dev] [PATCH 1/3] rte_sched: keep track of RED drops Stephen Hemminger
2015-11-29 22:12 ` Thomas Monjalon
2015-11-30 17:47 ` [dpdk-dev] [PATCH] rte_sched: drop deprecation notice for RED statistics Stephen Hemminger
2015-11-29 18:46 ` [dpdk-dev] [PATCH 2/3] rte_sched: introduce reciprocal divide Stephen Hemminger
2015-12-02 16:45 ` Dumitrescu, Cristian
2015-12-02 16:57 ` Hannes Frederic Sowa
2015-12-02 22:05 ` Stephen Hemminger
2015-11-29 18:46 ` [dpdk-dev] [PATCH 3/3] rte_sched: eliminate floating point in calculating byte clock Stephen Hemminger
2015-12-02 16:48 ` Dumitrescu, Cristian
2015-12-02 22:08 ` Stephen Hemminger
2016-03-04 15:00 ` [dpdk-dev] [PATCH 0/3] sched: patches for 2.2 Thomas Monjalon
2016-03-08 7:49 ` Dumitrescu, Cristian
2016-03-08 16:33 ` Stephen Hemminger
2016-03-08 19:53 ` Dumitrescu, Cristian
2016-03-08 20:40 ` Stephen Hemminger
2016-03-10 18:41 ` Dumitrescu, Cristian
2016-03-10 18:44 ` Stephen Hemminger [this message]
2016-03-10 18:51 ` Dumitrescu, Cristian
2016-03-13 22:25 ` Thomas Monjalon
2016-03-13 22:47 ` Dumitrescu, Cristian
2016-03-13 23:09 ` Thomas Monjalon
2016-03-14 14:40 ` Dumitrescu, Cristian
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=CAOaVG14oFvwpv_UVWKdN_JM+QDsvDqx9dZL77BToC0qqU1S3sg@mail.gmail.com \
--to=stephen@networkplumber.org \
--cc=cristian.dumitrescu@intel.com \
--cc=dev@dpdk.org \
/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).