From: Denys Vlasenko <vda.linux@googlemail.com>
To: herbert@gondor.apana.org.au, davem@davemloft.net,
linux-crypto@vger.kernel.org
Cc: Andrew Morton <akpm@linux-foundation.org>
Subject: Crypto patches
Date: Thu, 18 Oct 2007 12:28:13 +0100 [thread overview]
Message-ID: <200710181228.13569.vda.linux@googlemail.com> (raw)
Hi Herbert, Dave,
Sometime ago I sent a patch which makes twofish key setup
code much smaller (2.5 times). Currently, it is so much unrolled
that twofish module's code is ~35k on i386.
I am ok with people disagreeing with me and considering 35k
not too big. However, IIRC that patch was not reviewed
(I've got no reply) and I have no way of knowing whether
it was deemed unacceptable or just was lost in the churn.
I want to rediff and resend it. I also want to send patches
for other modules (e.g. camellia, aes).
Please let me know what is the best channels to send
crypto patches through so that they are not lost. Thanks.
--
vda
next reply other threads:[~2007-10-18 11:28 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-18 11:28 Denys Vlasenko [this message]
2007-10-18 15:03 ` Crypto patches Herbert Xu
2007-10-18 19:19 ` Sebastian Siewior
2007-10-20 4:57 ` Denys Vlasenko
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=200710181228.13569.vda.linux@googlemail.com \
--to=vda.linux@googlemail.com \
--cc=akpm@linux-foundation.org \
--cc=davem@davemloft.net \
--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.