From: Remy Horton <remy.horton@intel.com>
To: "Bodek, Zbigniew" <Zbigniew.Bodek@cavium.com>,
"dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] OpenSSL and non-BSD licenses in DPDK
Date: Thu, 1 Sep 2016 10:22:04 +0100 [thread overview]
Message-ID: <43149694-a5c3-1c30-5fd0-9bad7dc5bb81@intel.com> (raw)
In-Reply-To: <CO2PR07MB55661B360820ED7273EFE96FAE30@CO2PR07MB556.namprd07.prod.outlook.com>
Morning,
On 31/08/2016 18:26, Bodek, Zbigniew wrote:
[..]
> I would like to ask a question regarding code licensing and importing code that
> uses different license than BSD-like. Especially I'm curious about the code
> that goes with OpenSSL/SSLeay license. Is it allowed to import such sources
> (or derived work) to DPDK? I've seen some GPL stuff, mostly kernel modules from
> Intel. So what with the above mentioned OpenSSL?
It is not my call to make, but my guess is the answer will almost
certainly be "No". DPDK makes it way into commercial products, and the
companies concerned (well, their lawyers actually..) most likley won't
like the prospect of extra licencing conditions slipping in.
..Remy
prev parent reply other threads:[~2016-09-01 9:22 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-31 17:26 Bodek, Zbigniew
2016-08-31 18:08 ` Matthew Hall
2016-09-01 9:22 ` Remy Horton [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=43149694-a5c3-1c30-5fd0-9bad7dc5bb81@intel.com \
--to=remy.horton@intel.com \
--cc=Zbigniew.Bodek@cavium.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).