All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jari Ruusu <jariruusu@users.sourceforge.net>
To: Andi Kleen <ak@muc.de>, Linus Torvalds <torvalds@osdl.org>
Cc: Florian Bohrer <Florian.Bohrer@t-online.de>,
	linux-kernel@vger.kernel.org, discuss@x86-64.org
Subject: Re: [PATCH] AES x86-64-asm impl.
Date: Mon, 04 Oct 2004 14:51:19 +0300	[thread overview]
Message-ID: <41613937.8BF0FE0D@users.sourceforge.net> (raw)
In-Reply-To: m3acv4zz5f.fsf@averell.firstfloor.org

Andi Kleen wrote:
> Florian.Bohrer@t-online.de (Florian Bohrer) writes:
> > the asm-code is from Jari Ruusu (loop-aes).
> > the org. glue-code is from Fruhwirth Clemens.
> 
> Thanks. I will add it to the x86-64 patchkit.

Here we go again...

Linus promised that he will not merge my code, and I am quite happy with my
code not being anywhere near mainline linux cryptoapi.

Linus, please consider dropping this.

-- 
Jari Ruusu  1024R/3A220F51 5B 4B F9 BB D3 3F 52 E9  DB 1D EB E3 24 0E A9 DD

  parent reply	other threads:[~2004-10-04 11:51 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <2KWl4-wq-25@gated-at.bofh.it>
2004-10-02 19:41 ` [PATCH] AES x86-64-asm impl Andi Kleen
2004-10-04  2:15   ` dean gaudet
2004-10-04 11:51   ` Jari Ruusu [this message]
2004-10-04 12:09     ` Paolo Ciarrocchi
2004-10-04 12:20       ` Jari Ruusu
2004-10-04 12:23         ` Paolo Ciarrocchi
2004-10-04 12:32           ` Jari Ruusu
2004-10-04 12:35             ` Paolo Ciarrocchi
2004-10-04 18:58             ` [discuss] " Raul Miller
2004-10-04 19:26             ` Bill Davidsen
2004-10-04 21:20               ` Lee Revell
2004-10-05 15:00                 ` Bill Davidsen
2004-10-04 13:08     ` Andi Kleen
2004-10-05  0:35       ` Andy Lutomirski
2004-10-05  5:15         ` Linus Torvalds
2004-10-02 17:53 Florian Bohrer
2004-10-02 19:37 ` Lee Revell

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=41613937.8BF0FE0D@users.sourceforge.net \
    --to=jariruusu@users.sourceforge.net \
    --cc=Florian.Bohrer@t-online.de \
    --cc=ak@muc.de \
    --cc=discuss@x86-64.org \
    --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.