All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tom Lendacky <thomas.lendacky@amd.com>
To: Herbert Xu <herbert@gondor.apana.org.au>,
	Scot Doyle <lkml14@scotdoyle.com>
Cc: <davem@davemloft.net>, <linux-crypto@vger.kernel.org>
Subject: Re: [PATCH] crypto: ccp - Check for CCP before registering crypto algs
Date: Mon, 22 Sep 2014 10:07:39 -0500	[thread overview]
Message-ID: <54203B3B.70307@amd.com> (raw)
In-Reply-To: <20140915114709.GB4923@gondor.apana.org.au>

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@scotdoyle.com>
>>> Signed-off-by: Tom Lendacky <thomas.lendacky@amd.com>
>>
>> Tested-by: Scot Doyle <lkml14@scotdoyle.com>
>
> Patch applied.  Thanks!
>

Hi Herbert,

Can you push this patch into the 3.17 release?

Also, it should probably go into to the stable releases.  Is this
something that you request or should I take care of that?

Thanks,
Tom

  reply	other threads:[~2014-09-22 15:07 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-09-05 15:31 [PATCH] crypto: ccp - Check for CCP before registering crypto algs Tom Lendacky
2014-09-05 23:49 ` Scot Doyle
2014-09-15 11:47   ` Herbert Xu
2014-09-22 15:07     ` Tom Lendacky [this message]
2014-09-24  6:22       ` 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=54203B3B.70307@amd.com \
    --to=thomas.lendacky@amd.com \
    --cc=davem@davemloft.net \
    --cc=herbert@gondor.apana.org.au \
    --cc=linux-crypto@vger.kernel.org \
    --cc=lkml14@scotdoyle.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.