Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id ; Thu, 18 Oct 2001 21:19:21 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id ; Thu, 18 Oct 2001 21:19:12 -0400 Received: from [209.195.52.30] ([209.195.52.30]:45325 "HELO [209.195.52.30]") by vger.kernel.org with SMTP id ; Thu, 18 Oct 2001 21:18:52 -0400 Date: Thu, 18 Oct 2001 16:57:48 -0700 (PDT) From: David Lang To: John Alvord cc: linux-kernel@vger.kernel.org Subject: Re: MODULE_LICENSE and EXPORT_SYMBOL_GPL In-Reply-To: <9ttustkpmhc24c6q53bv5jghl3g257htdp@4ax.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 so are you saying that BSD licened modules are not going to be allowed to use any future entry points (assuming they are all put under the the export_symbol_gpl limits)? saying that existing stuff will not change doesn't answer the problem about licences that may have source avilable (tainting) but may not. if you assume either way you will cause a bunch of problems. David Lang On Thu, 18 Oct 2001, John Alvord wrote: > Date: Thu, 18 Oct 2001 17:46:18 -0700 > From: John Alvord > To: David Lang > Cc: linux-kernel@vger.kernel.org > Subject: Re: MODULE_LICENSE and EXPORT_SYMBOL_GPL > > On Thu, 18 Oct 2001 15:38:36 -0700 (PDT), David Lang > wrote: > > >so what will the export_symbol_gpl stuff do with the BSD license? it may > >or may not have source avilable so is it allowed to use the exported > >symbols or not? > > > >for the tainting module process there is the same problem. > > > >knowing the license the code was released under does not tell you if the > >source is available or not. > Linus said that all existing entry points would remain untagged. Thus > existing modules would not be affected. > > john > - 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/