From: Christoph Hellwig <hch@lst.de>
To: Doug Ledford <dledford@redhat.com>
Cc: torvalds@linux-foundation.org, linux-kernel@vger.kernel.org
Subject: Re: CQ and RDMA READ/WRITE APIs
Date: Mon, 16 May 2016 13:49:26 +0200 [thread overview]
Message-ID: <20160516114926.GA681@lst.de> (raw)
In-Reply-To: <743399f9-10b7-6e62-2bf4-6a8656df8a55@redhat.com>
[adding Linus and linux-kernel to Cc]
On Fri, May 13, 2016 at 08:04:17PM -0400, Doug Ledford wrote:
> You submitted new files into the subsystem under GPL only license in
> contrast to the rest of the subsystem. This presents a problem. I'm in
> the position where I need to either revert them, or I need your
> permission to make them dual license GPL/BSD to match the rest of the
> subsystem. Were you intentionally trying to make the OFED work illegal,
> or just an oversight?
Hi Doug,
the RDMA code was developed for a GPLed driver and moved to the code,
and lots of people contributed to it under the GPL, as they assumed
Linux code in genral is. Іf dual-licensing is possible at all it would
require a lot of work, which I don't think is worth it. If you don't
want GPL code in the core rdma.ko module we can move it to a rdma-gpl.ko
module, but that would be a little bit odd.
next parent reply other threads:[~2016-05-16 11:49 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <743399f9-10b7-6e62-2bf4-6a8656df8a55@redhat.com>
2016-05-16 11:49 ` Christoph Hellwig [this message]
2016-05-16 14:51 ` CQ and RDMA READ/WRITE APIs Doug Ledford
2016-05-16 17:46 ` Linus Torvalds
2016-05-16 18:23 ` Doug Ledford
[not found] ` <6633ce02-7983-ad09-f95d-03cea6f54e31-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2016-05-17 17:29 ` Bart Van Assche
2016-05-17 17:29 ` Bart Van Assche
[not found] ` <573B550D.5020008-XdAiOPVOjttBDgjK7y7TUQ@public.gmane.org>
2016-05-17 17:32 ` Doug Ledford
2016-05-17 17:32 ` Doug Ledford
2016-05-17 18:50 ` Linus Torvalds
[not found] ` <732fb772-2f21-3ac9-a35a-aa4383734df5-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2016-05-18 2:48 ` Parav Pandit
2016-05-18 2:48 ` Parav Pandit
[not found] ` <CAG53R5VSjz_G1adajcoUdgh3Sf1yyKf7UREFoNF9x_V+N6oR6A-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2016-05-18 14:07 ` Doug Ledford
2016-05-18 14:07 ` Doug Ledford
[not found] ` <43b558b1-8400-612c-9b27-6539be080871-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2016-05-18 15:54 ` Parav Pandit
2016-05-18 15:54 ` Parav Pandit
[not found] ` <CA+55aFzq+4DJL46B8PXQQG-DpNpzZNzk=O6j+8U_NC6H6BwTdQ-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2016-05-17 5:38 ` Christoph Hellwig
2016-05-17 5:38 ` Christoph Hellwig
2016-05-17 15:35 ` Christoph Lameter
2016-05-16 15:26 ` Doug Ledford
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=20160516114926.GA681@lst.de \
--to=hch@lst.de \
--cc=dledford@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.