From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: "Måns Rullgård" <mru@kth.se>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Linux 2.6.8-rc3 - BSD licensing
Date: Thu, 05 Aug 2004 21:21:21 +0100 [thread overview]
Message-ID: <1091737280.8366.1.camel@localhost.localdomain> (raw)
In-Reply-To: <yw1x7jsdh42d.fsf@kth.se>
On Iau, 2004-08-05 at 18:45, Måns Rullgård wrote:
> Assuming that the AES code is not in itself considered derived from
> the kernel, I see nothing preventing the source file in the kernel
> tree carrying a BSD license. Obviously, when used with the kernel the
> GPL will apply, but anyone would be free to take the AES code and
> reuse it under the BSD license. If, on the other hand, the AES source
> in the kernel only carries a GPL license tag, someone looking at it
> will not be aware that the code is (possibly) available with less
> restrictions form another source.
The random driver has an example of that kind of dual licensing made
explicit. Given code gets modified for the kernel maybe it would be
simpler to just give the URL of the original in the comments so everyone
else (who probably wants the original anyway) can grab it there.
next prev parent reply other threads:[~2004-08-05 21:25 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-03 22:09 Linux 2.6.8-rc3 Linus Torvalds
2004-08-04 12:07 ` Jan De Luyck
2004-08-04 12:13 ` Karol Kozimor
2004-08-04 12:40 ` Erik Mouw
2004-08-05 15:10 ` OGAWA Hirofumi
2004-08-05 22:19 ` szonyi calin
2004-08-04 12:57 ` Gene Heskett
2004-08-04 12:44 ` Juergen Stuber
2004-08-04 13:37 ` Geert Uytterhoeven
2004-08-04 15:04 ` Jari Ruusu
2004-08-04 16:00 ` James Morris
2004-08-04 16:10 ` J. Bruce Fields
2004-08-04 16:27 ` Arjan van de Ven
2004-08-04 18:19 ` Patrick McFarland
2004-08-04 18:45 ` Linus Torvalds
2004-08-05 13:54 ` Patrick McFarland
2004-08-04 21:27 ` H. Peter Anvin
2004-08-04 18:37 ` Linux 2.6.8-rc3 - BSD licensing Fruhwirth Clemens
2004-08-04 18:51 ` Linus Torvalds
2004-08-04 19:26 ` Fruhwirth Clemens
2004-08-04 19:56 ` Linus Torvalds
2004-08-05 12:33 ` Jari Ruusu
2004-08-05 16:50 ` Linus Torvalds
2004-08-05 17:45 ` Måns Rullgård
2004-08-05 20:21 ` Alan Cox [this message]
2004-08-05 21:37 ` Måns Rullgård
2004-08-05 21:08 ` Alan Cox
2004-08-06 9:47 ` Jari Ruusu
2004-08-06 16:39 ` Linus Torvalds
2004-08-07 10:19 ` Jari Ruusu
2004-08-07 10:38 ` Patrick McFarland
2004-08-07 17:27 ` Linus Torvalds
2004-08-05 12:32 ` Linux 2.6.8-rc3 Jari Ruusu
2004-08-04 16:23 ` Linus Torvalds
2004-08-05 15:04 ` [PATCH] Drop asm i586 AES code James Morris
2004-08-04 15:08 ` Linux 2.6.8-rc3 (compile stats) John Cherry
2004-08-04 18:52 ` [patch] 2.6.8-rc3: fix modular kernel with gcc 2.95 Adrian Bunk
2004-08-06 19:57 ` 2.6.8-rc3: MPT Fusion compile error with PROC_FS=n Adrian Bunk
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1091737280.8366.1.camel@localhost.localdomain \
--to=alan@lxorguk.ukuu.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=mru@kth.se \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox