From mboxrd@z Thu Jan 1 00:00:00 1970 From: "Steve Wise" Subject: RE: [PATCH] libibverbs: add ARM64 memory barrier macros Date: Fri, 20 May 2016 13:46:25 -0500 Message-ID: <011e01d1b2c7$e9a70c10$bcf52430$@opengridcomputing.com> References: <20160520163207.B99DCE0B9D@smtp.ogc.us> <9C6B67F36DCAFC479B1CF6A967258A8C7DDBB201@ORSMSX115.amr.corp.intel.com> <011001d1b2c6$a95a6f40$fc0f4dc0$@opengridcomputing.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <011001d1b2c6$a95a6f40$fc0f4dc0$@opengridcomputing.com> Content-Language: en-us Sender: linux-rdma-owner-u79uwXL29TY76Z2rM5mHXA@public.gmane.org To: "'Woodruff, Robert J'" , dledford-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org Cc: linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org List-Id: linux-rdma@vger.kernel.org > > Does this mean that the code you want to add to libibverbs will be tainted > with GPL > > since they come from the Linux kernel. > > I guess so. > > > I know that there are a lot of people that will not use a GPL library, since > it could > > taint their applications with GPL if they > > link to that library. I thought that is why LGPL was invented to prevent such > tainting. > > I could utilize the code from FreeBSD. Does that allow me to submit this to > libibverbs under the dual GPL/BSD license? > I think I can just re-implement these services myself based published works describing the memory barrier assembly for ARM (like the document Jason referenced earlier). That will avoid any tainting. Doug: Will that work? -- 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