From: Linus Torvalds <torvalds@linux-foundation.org>
To: Herbert Xu <herbert@gondor.apana.org.au>
Cc: "David S. Miller" <davem@davemloft.net>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Crypto Mailing List <linux-crypto@vger.kernel.org>
Subject: Re: Crypto Update for 2.6.28
Date: Wed, 24 Dec 2008 14:32:28 -0800 (PST) [thread overview]
Message-ID: <alpine.LFD.2.00.0812241432130.3535@localhost.localdomain> (raw)
In-Reply-To: <20081224222045.GA488@gondor.apana.org.au>
On Thu, 25 Dec 2008, Herbert Xu wrote:
>
> A regression has been reported where the new algorithm testing
> infrastructure may cause the optimised versions of AES to fail
> when it's built into the kernel (as opposed to as a module).
Can't we just get rid of that stupid testing infrastructure, or make it a
module-only thing? I refuse to pull a 1000+ line patch for something like
this, especially this late. It's insane.
Linus
next prev parent reply other threads:[~2008-12-24 22:33 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-21 2:43 Crypto Update for 2.6.26 Herbert Xu
2008-07-14 12:14 ` Crypto Update for 2.6.27 Herbert Xu
2008-10-10 7:09 ` Crypto Update for 2.6.28 Herbert Xu
2008-10-10 18:22 ` Linus Torvalds
2008-10-10 18:29 ` Randy Dunlap
2008-10-11 2:13 ` Herbert Xu
2008-11-25 8:58 ` [PATCH] crypto: fix error flow of crypto/testmgr.c:test_comp() Ingo Molnar
2008-11-25 15:20 ` Herbert Xu
2008-11-25 17:14 ` Ingo Molnar
2008-11-25 17:26 ` Patrick McHardy
2008-11-25 21:52 ` David Miller
2008-11-26 1:09 ` [warnings] 37 warning fixes in networking related files Ingo Molnar
2008-11-26 1:11 ` David Miller
2008-11-26 1:08 ` [PATCH] crypto: fix error flow of crypto/testmgr.c:test_comp() David Miller
2008-11-26 2:40 ` Ingo Molnar
2008-12-10 12:35 ` Crypto Update for 2.6.28 Herbert Xu
2008-12-24 22:20 ` Herbert Xu
2008-12-24 22:32 ` Linus Torvalds [this message]
2008-12-24 23:47 ` 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=alpine.LFD.2.00.0812241432130.3535@localhost.localdomain \
--to=torvalds@linux-foundation.org \
--cc=davem@davemloft.net \
--cc=herbert@gondor.apana.org.au \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®