DPDK patches and discussions
 help / color / mirror / Atom feed
From: "Bodek, Zbigniew" <Zbigniew.Bodek@cavium.com>
To: "dev@dpdk.org" <dev@dpdk.org>
Subject: [dpdk-dev] OpenSSL and non-BSD licenses in DPDK
Date: Wed, 31 Aug 2016 17:26:41 +0000	[thread overview]
Message-ID: <CO2PR07MB55661B360820ED7273EFE96FAE30@CO2PR07MB556.namprd07.prod.outlook.com> (raw)

Hello Everyone,

First of all I would like to say hello since this is my first e-mail to this
mailing list.

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?

Thank you in advance for your answers.

Kind regards
Zbigniew

             reply	other threads:[~2016-08-31 17:26 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-08-31 17:26 Bodek, Zbigniew [this message]
2016-08-31 18:08 ` Matthew Hall
2016-09-01  9:22 ` Remy Horton

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=CO2PR07MB55661B360820ED7273EFE96FAE30@CO2PR07MB556.namprd07.prod.outlook.com \
    --to=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).