All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sebastian Siewior <linux-crypto@ml.breakpoint.cc>
To: Herbert Xu <herbert@gondor.apana.org.au>
Cc: linux-crypto@vger.kernel.org
Subject: [patch 0/2] merge AES setkey function for i586
Date: Sat, 03 Nov 2007 11:05:03 +0100	[thread overview]
Message-ID: <20071102180503.712394234@ml.breakpoint.cc> (raw)

Hello Herbert,

this patch series unifies the AES setkey function for the i586 asm code. 
Now the glue code is equal for aes_{32|64} and can be shared as well.

Sebastian
-- 

             reply	other threads:[~2007-11-03 10:05 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-11-03 10:05 Sebastian Siewior [this message]
2007-11-03 10:05 ` [patch 1/2] AES i586, remove setkey Sebastian Siewior
2007-11-10 11:31   ` Herbert Xu
2007-11-03 10:05 ` [patch 2/2] remove similar aes glue code Sebastian Siewior
2007-11-10 11:19   ` Herbert Xu
2007-11-10 21:20     ` Sebastian Siewior
2007-11-11  1:18       ` Herbert Xu
2007-11-26  9:35         ` Sebastian Siewior
2007-11-26 10:32           ` Herbert Xu
2007-11-27 19:31             ` [PATCH] [crypto] " Sebastian Siewior
2007-11-29 13:15               ` 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=20071102180503.712394234@ml.breakpoint.cc \
    --to=linux-crypto@ml.breakpoint.cc \
    --cc=herbert@gondor.apana.org.au \
    --cc=linux-crypto@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.