All of lore.kernel.org
 help / color / mirror / Atom feed
From: Linus Torvalds <torvalds@osdl.org>
To: Patrick McFarland <diablod3@gmail.com>
Cc: arjanv@redhat.com, "J. Bruce Fields" <bfields@fieldses.org>,
	James Morris <jmorris@redhat.com>,
	Jari Ruusu <jariruusu@users.sourceforge.net>,
	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 11:45:12 -0700 (PDT)	[thread overview]
Message-ID: <Pine.LNX.4.58.0408041130530.24588@ppc970.osdl.org> (raw)
In-Reply-To: <d577e56904080411192f17e508@mail.gmail.com>



On Wed, 4 Aug 2004, Patrick McFarland wrote:
> 
> So will 2.6.8-rc4 be released with no optimized aes, or with a saner
> optimized aes?

We'll see just how quickly somebody steps up to the plate. I spent some
time taking the original Gladman source into gas format, and have a really
ugly (untested) direct conversion if somebody wants to work on it.

Side note: Jari Ruusu has himself been distributing the code he now 
objects to as part of his own linux kernel loop-aes patches. From the 
loop-aes README:

	Copyright 2001,2002,2003,2004 by Jari Ruusu.
	Redistribution of this file is permitted under the GNU Public License.

But the original x86 assembler code that is part of that loop-aes patch
was copyright Dr Brian Gladman, and was NOT originally under the GPL, so
it was Jari Ruusu who originally did something very suspect from a
copyright angle. Now he claims he never wanted to GPL it, but the fact is,
he's been distributing kernel patches with the code for a long time, and
claiming it is GPL'd.

So then David and James wanted to include it into the kernel as part of
the standard encryption layer, and I said no, since I felt the copyright
wasn't clear. So James asked Dr Gladman for permission to dual-license
under the GPL, and got it. So I was happy.

Now Jari Ruusu comes along and starts complaining about things. 

Jari: mitä helvetin järkeä tuossa on? Selitä.

		Linus

  reply	other threads:[~2004-08-04 18:46 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 [this message]
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=Pine.LNX.4.58.0408041130530.24588@ppc970.osdl.org \
    --to=torvalds@osdl.org \
    --cc=arjanv@redhat.com \
    --cc=bfields@fieldses.org \
    --cc=clemens@endorphin.org \
    --cc=davem@redhat.com \
    --cc=diablod3@gmail.com \
    --cc=jariruusu@users.sourceforge.net \
    --cc=jmorris@redhat.com \
    --cc=linux-kernel@vger.kernel.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.