DPDK patches and discussions
 help / color / mirror / Atom feed
From: "Zhang, Helin" <helin.zhang@intel.com>
To: Stephen Hemminger <stephen@networkplumber.org>
Cc: "dev@dpdk.org" <dev@dpdk.org>,
	"Bernal Marin, Miguel" <miguel.bernal.marin@intel.com>
Subject: Re: [dpdk-dev] Headers files with BSD license in kernel
Date: Wed, 10 Jun 2015 01:20:25 +0000	[thread overview]
Message-ID: <F35DEAC7BCE34641BA9FAC6BCA4A12E70A87E0F2@SHSMSX104.ccr.corp.intel.com> (raw)
In-Reply-To: <20150609181528.0053039d@urahara>



> -----Original Message-----
> From: Stephen Hemminger [mailto:stephen@networkplumber.org]
> Sent: Wednesday, June 10, 2015 9:15 AM
> To: Zhang, Helin
> Cc: Miguel Bernal Marin; dev@dpdk.org; Bernal Marin, Miguel
> Subject: Re: [dpdk-dev] Headers files with BSD license in kernel
> 
> On Wed, 10 Jun 2015 00:42:59 +0000
> "Zhang, Helin" <helin.zhang@intel.com> wrote:
> 
> > Hi Miguel
> >
> > My thought is there might be something wrong. Let's see what comments from
> other experts!
> > Thank you very much for the good catch!
> >
> > Regards,
> > Helin
> >
> > > -----Original Message-----
> > > From: Miguel Bernal Marin
> > > [mailto:miguel.bernal.marin@linux.intel.com]
> > > Sent: Wednesday, June 10, 2015 4:10 AM
> > > To: dev@dpdk.org
> > > Cc: david.marchand@6wind.com; Burakov, Anatoly; Zhang, Helin; Bernal
> > > Marin, Miguel
> > > Subject: Re: [dpdk-dev] Headers files with BSD license in kernel
> > >
> > > Including maintainers in CC
> > >
> > > On Tue, Jun 09, 2015 at 12:40:57PM -0500, Miguel Bernal Marin wrote:
> > > > Hi,
> > > >
> > > > I'm working on Clear Linux project, and when I was integrating
> > > > DPDK kernel modules to our kernel I found there are two headers
> > > > with BSD License
> > > >
> > > > rte_pci_dev_feature_defs.h
> > > > rte_pci_dev_features.h
> > > >
> > > > those are included in igb_uio module.
> > > >
> > > > Are those licenses correct?
> > > >
> > > > Thanks,
> > > > Miguel
> > > >
> 
> You can always escalate a BSD license to GPL, but the other way is not allowed.
> Ideally, the language on the file should make it clear that it is dual licensed.
> In an ideal world, igb_uio would go away, I am working on that.

Yes, I agree with you. To be clearer, rte_pci_dev_feature_defs.h should be in dual liceses, and rte_pci_dev_features.h should be in GPL license.

Thanks,
Helin

  reply	other threads:[~2015-06-10  1:20 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-09 17:40 Miguel Bernal Marin
2015-06-09 20:09 ` Miguel Bernal Marin
2015-06-10  0:42   ` Zhang, Helin
2015-06-10  1:15     ` Stephen Hemminger
2015-06-10  1:20       ` Zhang, Helin [this message]
2015-06-10  8:54         ` Thomas Monjalon
2015-06-10  9:01           ` Burakov, Anatoly
2015-06-10  9:08             ` 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=F35DEAC7BCE34641BA9FAC6BCA4A12E70A87E0F2@SHSMSX104.ccr.corp.intel.com \
    --to=helin.zhang@intel.com \
    --cc=dev@dpdk.org \
    --cc=miguel.bernal.marin@intel.com \
    --cc=stephen@networkplumber.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).