public inbox for linux-rdma@vger.kernel.org
 help / color / mirror / Atom feed
From: Doug Ledford <dledford-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
To: Christoph Hellwig <hch-jcswGhMUV9g@public.gmane.org>,
	linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
	Bart Van Assche
	<bart.vanassche-XdAiOPVOjttBDgjK7y7TUQ@public.gmane.org>,
	Sagi Grimberg <sagi-NQWnxTmZq1alnMjI0IkVqw@public.gmane.org>
Subject: Re: [hch-jcswGhMUV9g@public.gmane.org: Re: CQ and RDMA READ/WRITE APIs]
Date: Mon, 16 May 2016 11:20:20 -0400	[thread overview]
Message-ID: <9a67fdac-88c2-ce29-f56b-e4d906a01518@redhat.com> (raw)
In-Reply-To: <20160516124838.GA1896-jcswGhMUV9g@public.gmane.org>

[-- Attachment #1: Type: text/plain, Size: 2124 bytes --]

On 05/16/2016 08:48 AM, Christoph Hellwig wrote:
> Sorry, forgot linux-rdma.  Please reply on the main thread on linux-kernel
> instead of here.

Indeed.  And I please need Sagi and Bart to comment on the linux-kernel
thread about this issue.  Please provide your acknowledgment of this
effective licensing change of your respective code bases.

> 
> ----- Forwarded message from Christoph Hellwig <hch-jcswGhMUV9g@public.gmane.org> -----
> 
> Date: Mon, 16 May 2016 13:49:26 +0200
> From: Christoph Hellwig <hch-jcswGhMUV9g@public.gmane.org>
> Subject: Re: CQ and RDMA READ/WRITE APIs
> To: Doug Ledford <dledford-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
> Cc: torvalds-de/tnXTf+JLsfHDXvbKv3WD2FQJk+8+b@public.gmane.org, linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
> 
> [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.
> 
> ----- End forwarded message -----
> --
> To unsubscribe from this list: send the line "unsubscribe linux-rdma" in
> the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> 


-- 
Doug Ledford <dledford-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
              GPG KeyID: 0E572FDD



[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 884 bytes --]

      parent reply	other threads:[~2016-05-16 15:20 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-05-16 12:48 [hch-jcswGhMUV9g@public.gmane.org: Re: CQ and RDMA READ/WRITE APIs] Christoph Hellwig
     [not found] ` <20160516124838.GA1896-jcswGhMUV9g@public.gmane.org>
2016-05-16 15:20   ` Doug Ledford [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=9a67fdac-88c2-ce29-f56b-e4d906a01518@redhat.com \
    --to=dledford-h+wxahxf7alqt0dzr+alfa@public.gmane.org \
    --cc=bart.vanassche-XdAiOPVOjttBDgjK7y7TUQ@public.gmane.org \
    --cc=hch-jcswGhMUV9g@public.gmane.org \
    --cc=linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=sagi-NQWnxTmZq1alnMjI0IkVqw@public.gmane.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