User: Password:
|
|
Subscribe / Log in / New account

Re: Initcall ordering problem (TTY vs modprobe vs MD5) and cryptomgr problem

From:  Linus Torvalds <torvalds-AT-linux-foundation.org>
To:  Herbert Xu <herbert-AT-gondor.hengli.com.au>
Subject:  Re: Initcall ordering problem (TTY vs modprobe vs MD5) and cryptomgr problem
Date:  Thu, 5 Aug 2010 21:20:02 -0700
Message-ID:  <AANLkTimVOkAi1_G9B290fHRR3PbV4H9003VarAv_zbGn@mail.gmail.com>
Cc:  David Howells <dhowells-AT-redhat.com>, gregkh-AT-suse.de, linux-kernel-AT-vger.kernel.org, linux-crypto-AT-vger.kernel.org
Archive-link:  Article

On Thu, Aug 5, 2010 at 7:35 PM, Herbert Xu <herbert@gondor.hengli.com.au> wrote:
>
> Because it can save data.  Each cryptographic algorithm (such as
> AES) may have multiple impelmentations, some of which are hardware-
> based.

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.

                      Linus


(Log in to post comments)


Copyright © 2010, Eklektix, Inc.
Comments and public postings are copyrighted by their creators.
Linux is a registered trademark of Linus Torvalds