From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S932222AbcEROID (ORCPT ); Wed, 18 May 2016 10:08:03 -0400 Received: from mx1.redhat.com ([209.132.183.28]:58857 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751062AbcEROIB (ORCPT ); Wed, 18 May 2016 10:08:01 -0400 Subject: Re: CQ and RDMA READ/WRITE APIs To: Parav Pandit References: <743399f9-10b7-6e62-2bf4-6a8656df8a55@redhat.com> <20160516114926.GA681@lst.de> <6633ce02-7983-ad09-f95d-03cea6f54e31@redhat.com> <573B550D.5020008@sandisk.com> <732fb772-2f21-3ac9-a35a-aa4383734df5@redhat.com> Cc: Bart Van Assche , Linus Torvalds , Christoph Hellwig , Linux Kernel Mailing List , Sagi Grimberg , "linux-rdma@vger.kernel.org" From: Doug Ledford Openpgp: id=AE6B1BDA122B23B4265B1274B826A3330E572FDD; url=pgp.mit.edu X-Enigmail-Draft-Status: N1110 Organization: Red Hat, Inc. Message-ID: <43b558b1-8400-612c-9b27-6539be080871@redhat.com> Date: Wed, 18 May 2016 10:07:58 -0400 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Thunderbird/45.0 MIME-Version: 1.0 In-Reply-To: Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="69lGFkcT8niputCsg8Jww0J6n669EtsUC" X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.5.16 (mx1.redhat.com [10.5.110.25]); Wed, 18 May 2016 14:08:00 +0000 (UTC) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --69lGFkcT8niputCsg8Jww0J6n669EtsUC Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable On 05/17/2016 10:48 PM, Parav Pandit wrote: > Hi Doug, >=20 > On Tue, May 17, 2016 at 11:02 PM, Doug Ledford wr= ote: >> Nice catch there Bart. That was well before my role as maintainer and= >> so settles things well enough for me. IOW, I don't feel I need to wor= ry >> about trying to maintain the dual license nature of the RDMA stack as = it >> was broken long before I took over. Thanks for pointing that out. >> >=20 > Does it mean we can submit new code files under GPL only license? You always could. > I submitted RDMA cgroup related code in ib_core under GPLv2 only licens= e. You did and you didn't. For instance, in patch 1/3, the new cgroup_rdma.c file has a notice of GPLv2, but no notice of copyright, so it's incomplete. You need to put a copyright notice in the file too. And in the file cgroup_rdma.h you have neither a copyright notice or a license statement. It's a plain file. In patch 2/3, the file infiniband/core/cgroup.c has a copied dual license (not necessary, it can be GPL only), but again, it is missing the copyright notice. You need to finish the conversation you and Christoph were having in that thread, but you also need a v11 of the patchset that fixes the copyright issues. > Existing files which are calling those new APIs will continue to be > dual license (similar to CQ and RDMA APIs)? Yes. --=20 Doug Ledford GPG KeyID: 0E572FDD --69lGFkcT8niputCsg8Jww0J6n669EtsUC Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iQIcBAEBCAAGBQJXPHc+AAoJELgmozMOVy/dg2QP/095MIe2xa7bcCrqAo3SEO8A fAjoZHG4HBauES6leLIU4rse+uv0Dmz7aRqEwugfl5xZ6RlMQdqRXKdmoHCjvYuT XgQRDCGLMEKad1Kil4I93dsqVragiihjFBFGmZCmj1Zb/oLvzvstumr5LFgRmA2X z0JD10Bx9vG7gI9RO9hN/Wq8sHr54sRA4dZLKpHM3XT0TrXw6wkWOLhFmvE8Fqdn E0kf3vaUabCvo0gkROkIwY+qd8jQkNCFCDC3t/fvj5BFBMf7lJb5yVLRdg++wkma yT/dE9zSfdgX7k2dRhmH8gsaEwSLdDg2zOgE5MbyK+XqLny5eRx3x01TsLN9B29j rfPpjJIdui57PnWk4SKqNtSg/86wazUFuEIuct4xY84UL7tucWTjRKD6e3GCT64E JNehRxxGXwX9zJjDkw4X6LWn+CQtP0S2wJbNuealPupmNiN0XZTOn88vDNvUEpCH NOsz5g8sVHLQ+/XYiBmlkOFGmIltwr31KyUPhQglXZ2JOWia4UkpLcxZxlZ3EBgb j1hRpiieJD+dEtl+cRcAGIOvikW/6GjDHciocvnlGIPkk2uko+xhzHEzKQK1e1OO PSzRL6YRu53lO2vfpbDoWMygI64cQ7P1TS7Vst87AD/y96Cjoy2SJ1Ezcr7j9U9e gG5qROoFL63ND1ke47Cb =Oosk -----END PGP SIGNATURE----- --69lGFkcT8niputCsg8Jww0J6n669EtsUC--