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 +, 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
On 09/15/2014 06:47 AM, Herbert Xu wrote:
On Fri, Sep 05, 2014 at 11:49:38PM +, 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
On Fri, Sep 05, 2014 at 11:49:38PM +, 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
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
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
