On Mon, Sep 22, 2014 at 10:07:39AM -0500, Tom Lendacky wrote: > On 09/15/2014 06:47 AM, Herbert Xu wrote: > >On Fri, Sep 05, 2014 at 11:49:38PM +0000, Scot Doyle wrote: > >> > >>On Fri, 5 Sep 2014, Tom Lendacky wrote: > >> > >>>If the ccp is built as a built-in module, then ccp-crypto (whether > >>>built as a module or a built-in module) will be able to load and > >>>it will register its crypto algorithms. If the system does not have > >>>a CCP this will result in -ENODEV being returned whenever a command > >>>is attempted to be queued by the registered crypto algorithms. > >>> > >>>Add an API, ccp_present(), that checks for the presence of a CCP > >>>on the system. The ccp-crypto module can use this to determine if it > >>>should register it's crypto alogorithms. > >>> > >>>Reported-by: Scot Doyle <lkml14@xxxxxxxxxxxxx> > >>>Signed-off-by: Tom Lendacky <thomas.lendacky@xxxxxxx> > >> > >>Tested-by: Scot Doyle <lkml14@xxxxxxxxxxxxx> > > > >Patch applied. Thanks! > > > > Hi Herbert, > > Can you push this patch into the 3.17 release? Thanks for the note, I've moved the patch to the crypto tree. Cheers, -- Email: Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxx> Home Page: http://gondor.apana.org.au/~herbert/ PGP Key: http://gondor.apana.org.au/~herbert/pubkey.txt -- To unsubscribe from this list: send the line "unsubscribe linux-crypto" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
