From: Gary R Hook <ghook@amd.com>
To: Paul Bolle <pebolle@tiscali.nl>, Jiri Kosina <trivial@kernel.org>
Cc: Tom Lendacky <thomas.lendacky@amd.com>,
Gary Hook <gary.hook@amd.com>, <linux-crypto@vger.kernel.org>,
<linux-kernel@vger.kernel.org>
Subject: Re: [PATCH][TRIVIAL] crypto: ccp - fix typo "CPP"
Date: Thu, 20 Oct 2016 15:44:13 -0500 [thread overview]
Message-ID: <031f3758-cef1-e237-e155-5e83cde9c304@amd.com> (raw)
In-Reply-To: <1476991259-4061-1-git-send-email-pebolle@tiscali.nl>
On 10/20/2016 02:20 PM, Paul Bolle wrote:
> The abbreviation for Cryptographic Coprocessor is "CCP".
>
> Signed-off-by: Paul Bolle <pebolle@tiscali.nl>
Acked-by: Gary R Hook <gary.hook@amd.com>
> ---
> include/linux/ccp.h | 6 +++---
> 1 file changed, 3 insertions(+), 3 deletions(-)
>
> diff --git a/include/linux/ccp.h b/include/linux/ccp.h
> index a7653339fedb..c71dd8fa5764 100644
> --- a/include/linux/ccp.h
> +++ b/include/linux/ccp.h
> @@ -11,8 +11,8 @@
> * published by the Free Software Foundation.
> */
>
> -#ifndef __CPP_H__
> -#define __CPP_H__
> +#ifndef __CCP_H__
> +#define __CCP_H__
>
> #include <linux/scatterlist.h>
> #include <linux/workqueue.h>
> @@ -553,7 +553,7 @@ enum ccp_engine {
> #define CCP_CMD_PASSTHRU_NO_DMA_MAP 0x00000002
>
> /**
> - * struct ccp_cmd - CPP operation request
> + * struct ccp_cmd - CCP operation request
> * @entry: list element (ccp driver use only)
> * @work: work element used for callbacks (ccp driver use only)
> * @ccp: CCP device to be run on (ccp driver use only)
>
--
This is my day job. Follow me at:
IG/Twitter/Facebook: @grhookphoto
IG/Twitter/Facebook: @grhphotographer
next prev parent reply other threads:[~2016-10-20 20:44 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-20 19:20 [PATCH][TRIVIAL] crypto: ccp - fix typo "CPP" Paul Bolle
2016-10-20 20:44 ` Gary R Hook [this message]
2016-10-25 3:46 ` 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=031f3758-cef1-e237-e155-5e83cde9c304@amd.com \
--to=ghook@amd.com \
--cc=gary.hook@amd.com \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pebolle@tiscali.nl \
--cc=thomas.lendacky@amd.com \
--cc=trivial@kernel.org \
/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.