All of lore.kernel.org
 help / color / mirror / Atom feed
From: "J. Bruce Fields" <bfields@fieldses.org>
To: James Morris <jmorris@redhat.com>
Cc: Jari Ruusu <jariruusu@users.sourceforge.net>,
	Linus Torvalds <torvalds@osdl.org>,
	Kernel Mailing List <linux-kernel@vger.kernel.org>,
	"David S. Miller" <davem@redhat.com>,
	Fruhwirth Clemens <clemens@endorphin.org>
Subject: Re: Linux 2.6.8-rc3
Date: Wed, 4 Aug 2004 12:10:46 -0400	[thread overview]
Message-ID: <20040804161046.GD19282@fieldses.org> (raw)
In-Reply-To: <Xine.LNX.4.44.0408041156310.9291-100000@dhcp83-76.boston.redhat.com>

On Wed, Aug 04, 2004 at 12:00:26PM -0400, James Morris wrote:
> On Wed, 4 Aug 2004, Jari Ruusu wrote:
> 
> > Linus Torvalds wrote:
> > > Summary of changes from v2.6.8-rc2 to v2.6.8-rc3
> > [snip]
> > > James Morris:
> > >   o [CRYPTO]: Add i586 optimized AES
> > 
> > My work on aes-i586.S is only licensed under original three clause BSD
> > license. You do not have my permission to change the license.
> > 
> > Either use original license or drop this code.
> 
> Can you assert licensing restrictions which override the original author's
> (Brian Gladman)?  I don't know the answer, just asking.

Well, the license is an "or", so you're free to create derived works
under either or both licenses as you prefer.

But I don't even see why it's an issue; every source I've ever seen
seems to agree that the two are compatible, so you're always free to
relicense under 3-clause BSD under BSD or GPL anyway.  So, unless I'm
missing something, the "or GPL" probably doesn't do anything more than
make explicit something that was allowed already.

--Bruce Fields

  reply	other threads:[~2004-08-04 16:11 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 [this message]
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
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=20040804161046.GD19282@fieldses.org \
    --to=bfields@fieldses.org \
    --cc=clemens@endorphin.org \
    --cc=davem@redhat.com \
    --cc=jariruusu@users.sourceforge.net \
    --cc=jmorris@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@osdl.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.