|| ||Linus Torvalds <torvalds-AT-linux-foundation.org> |
|| ||Herbert Xu <herbert-AT-gondor.hengli.com.au> |
|| ||Re: Initcall ordering problem (TTY vs modprobe vs MD5) and cryptomgr
|| ||Thu, 5 Aug 2010 21:20:02 -0700|
|| ||David Howells <dhowells-AT-redhat.com>, gregkh-AT-suse.de,
|| ||Article, Thread
On Thu, Aug 5, 2010 at 7:35 PM, Herbert Xu <firstname.lastname@example.org> wrote:
> Because it can save data. Each cryptographic algorithm (such as
> AES) may have multiple impelmentations, some of which are hardware-
Umm. The _developer_ had better test the thing. That is absolutely
_zero_ excuse for then forcing every boot for every poor user to re-do
the test over and over again.
Guys, this comes up every single time: you as a developer may think
that your code is really important, but get over yourself already.
It's not so important that everybody must be forced to do it.
to post comments)