Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id ; Wed, 20 Nov 2002 14:34:24 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id ; Wed, 20 Nov 2002 14:34:24 -0500 Received: from astound-64-85-224-253.ca.astound.net ([64.85.224.253]:57605 "EHLO master.linux-ide.org") by vger.kernel.org with ESMTP id ; Wed, 20 Nov 2002 14:34:22 -0500 Date: Wed, 20 Nov 2002 11:40:47 -0800 (PST) From: Andre Hedrick To: Cort Dougan cc: Alan Cox , Xavier Bestel , Mark Mielke , Rik van Riel , David McIlwraith , Linux Kernel Mailing List Subject: Re: spinlocks, the GPL, and binary-only modules In-Reply-To: <20021120123145.B17249@duath.fsmlabs.com> Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1500 Lines: 37 On Wed, 20 Nov 2002, Cort Dougan wrote: > } This can be made clean if all the inlined C in the headers are pushed > } back to an actual .c file and the make it function to call as an extern. > } So the solution is to make a patch and publish that patch which cleans the > } out the C code in question and move the associacted GPL license to the new > } .c files. This is proper and legal as structs are just the glue or api. > } > } So if I publish this patch where it can be freely available for usage by > } all, I comply with GPL. This also removes any of the "extremists" points > } of the smallest amount of GPL code invoked by the compiler can not touch > } pure code. > } > } Any arguments why this will not work? > > Maybe something else would be better. Adding -fno-inline to the build > might be more useful. It makes things a bit cleaner. > > It's a nasty mess to have to do this for every subsystem when someone gets > a wild-hair and starts inline-ing things without thinking. Well since there is a fork for everything else, how about a business-linux-2.{4,5} fork? As a place to make it even harder for the extremist to whine and cry over the usages of binary only modules. Comments? Andre Hedrick LAD Storage Consulting Group - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/