All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andi Kleen <ak@suse.de>
To: Joachim Fritschi <jfritschi@freenet.de>
Cc: linux-kernel@vger.kernel.org, linux-crypto@vger.kernel.org,
	herbert@gondor.apana.org.au
Subject: Re: [PATCH  1/4] Twofish cipher - split out common c code
Date: Thu, 8 Jun 2006 03:15:15 +0200	[thread overview]
Message-ID: <200606080315.15067.ak@suse.de> (raw)
In-Reply-To: <200606072137.24176.jfritschi@freenet.de>

On Wednesday 07 June 2006 21:37, Joachim Fritschi wrote:
> On Sunday 04 June 2006 15:16, Joachim Fritschi wrote:
> > I have revised my initial twofish assembler patchset according to the 
> > criticims i recieved on this list:
> > This patch splits up the twofish crypto routine into a common part ( key 
> > setup  ) which will be uses by all twofish crypto modules ( generic-c , i586 
> > assembler and x86_64 assembler ) and generic-c part. It also creates a new 
> > header file which will be used by all 3 modules. 
> > This eliminates all code duplication.
> > Correctness was verified with the tcrypt module and automated test scripts.
> My first mail was wordwrapped. This one should be unwrapped and working:

Thanks I merged them all now.

-Andi

  reply	other threads:[~2006-06-08  1:25 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-06-04 13:16 [PATCH 1/4] Twofish cipher - split out common c code Joachim Fritschi
2006-06-07 19:37 ` Joachim Fritschi
2006-06-08  1:15   ` Andi Kleen [this message]
2006-06-08  1:57   ` Herbert Xu
2006-06-08  7:20     ` Joachim Fritschi
2006-06-08  7:27       ` Herbert Xu
2006-06-16 11:58         ` Joachim Fritschi
2006-06-18 11:31           ` Herbert Xu
2006-06-18 13:53             ` Roman Zippel
2006-06-19  6:18               ` Herbert Xu
2006-06-19 14:12                 ` Joachim Fritschi
2006-06-20 10:26                   ` Herbert Xu
2006-06-20 10:27                     ` Herbert Xu

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=200606080315.15067.ak@suse.de \
    --to=ak@suse.de \
    --cc=herbert@gondor.apana.org.au \
    --cc=jfritschi@freenet.de \
    --cc=linux-crypto@vger.kernel.org \
    --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.