Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id ; Sat, 4 Jan 2003 23:03:12 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id ; Sat, 4 Jan 2003 23:03:12 -0500 Received: from viefep16-int.chello.at ([213.46.255.17]:58148 "EHLO viefep16-int.chello.at") by vger.kernel.org with ESMTP id ; Sat, 4 Jan 2003 23:03:11 -0500 Message-ID: <031101c2b470$93791cc0$6400a8c0@twister> From: "NEURONET" To: References: <3E179CCF.F4CAE1E5@digeo.com> <02a101c2b46a$47d79900$6400a8c0@twister> Subject: Re: Linux iSCSI Initiator, OpenSource (fwd) (Re: Gauntlet Set NOW!) Date: Sun, 5 Jan 2003 05:11:51 +0100 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2720.3000 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000 Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 897 Lines: 22 > > If there really is inlined functionality which we do not wish made > > available to non-GPL modules then it should be either uninlined and > > not exported or it should be wrapped in #ifdef GPL. > > I don't even think there should be any such case, > as the real point in having LGPL is, supposedly, to > support *interfacing*, so using headers (source-code > *interfaces*) and linking to stuff (binding binary > *interfaces*) should be just fine under LGPL (or a > better LGPL? IGPL? dunno the details that deep, sorry). (Umm, sorry, I guess I should've been sleeping fast already, instead of confusing things publicly here... :-/ ) Sab - 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/