> 14USA-18X Serial Adapter. Distribution and/or
> Modification of the
> 15keyspan.c driver which includes this firmware, in whole
> or in part,
> 16requires the inclusion of this statement."
> 17
> 18 */
> with a surelly non-free/non-GPL license.
That one is being sorted out current
Alan Cox wrote:
>
> > Well, would it be possible to create some module under LGPL, and then
> > have included it into the kernel? Maybe it needs to maintain the LGPL
> > version out of the kernel, and transform a copy to the GPL before
> > submitting?
>
> There is kernel code under a whole varie
> Well, would it be possible to create some module under LGPL, and then
> have included it into the kernel? Maybe it needs to maintain the LGPL
> version out of the kernel, and transform a copy to the GPL before
> submitting?
There is kernel code under a whole variety of licenses. When linked tog
Hi,
mirabilos wrote:
> > > It whould nice also if we include the type of the license (GPL,...).
> > > This for a fast parsing (and maybe also to replace the few lines
> > > of license)
> > Is there any kernel code that isn't GPLed?
> It must not, due to the GPL viral effect.
Well, would it be p
Giacomo A. Catenazzi <[EMAIL PROTECTED]>:
> We should use the same filed name of CREDITS e.g. D: for Description.
> (maybe you can invert D: description and T: time of last update)
Good point.
> It whould nice also if we include the type of the license (GPL,...).
> This for a fast parsing (and
"Eric S. Raymond" wrote:
>
> This is a proposal for an attribution metadata system in the Linux kernel
> sources. The goal of the system is to make it easy for people reading
> any given piece of code to identify the responsible maintainer. The motivation
> for this proposal is that the present
6 matches
Mail list logo
