From: Haren Myneni <haren@linux.vnet.ibm.com>
To: Colin King <colin.king@canonical.com>
Cc: Haren Myneni <haren@us.ibm.com>,
Herbert Xu <herbert@gondor.apana.org.au>,
"David S . Miller" <davem@davemloft.net>,
Benjamin Herrenschmidt <benh@kernel.crashing.org>,
Paul Mackerras <paulus@samba.org>,
Michael Ellerman <mpe@ellerman.id.au>,
linux-crypto@vger.kernel.org, linuxppc-dev@lists.ozlabs.org,
kernel-janitors@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH][V2] crypto/nx: fix spelling mistake: "availavle" -> "available"
Date: Tue, 14 Nov 2017 18:20:03 +0000 [thread overview]
Message-ID: <5A0B33D3.4010707@linux.vnet.ibm.com> (raw)
In-Reply-To: <20171114143217.21456-1-colin.king@canonical.com>
Sorry for my mistake. Thanks.
Acked-by: Haren Myneni <haren@us.ibm.com>
On 11/14/2017 06:32 AM, Colin King wrote:
> From: Colin Ian King <colin.king@canonical.com>
>
> Trivial fix to spelling mistake in pr_err error message text. Also
> fix spelling mistake in proceeding comment.
>
> Signed-off-by: Colin Ian King <colin.king@canonical.com>
> ---
> drivers/crypto/nx/nx-842-powernv.c | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/crypto/nx/nx-842-powernv.c b/drivers/crypto/nx/nx-842-powernv.c
> index f2246a5abcf6..1e87637c412d 100644
> --- a/drivers/crypto/nx/nx-842-powernv.c
> +++ b/drivers/crypto/nx/nx-842-powernv.c
> @@ -743,8 +743,8 @@ static int nx842_open_percpu_txwins(void)
> }
>
> if (!per_cpu(cpu_txwin, i)) {
> - /* shoudn't happen, Each chip will have NX engine */
> - pr_err("NX engine is not availavle for CPU %d\n", i);
> + /* shouldn't happen, Each chip will have NX engine */
> + pr_err("NX engine is not available for CPU %d\n", i);
> return -EINVAL;
> }
> }
>
WARNING: multiple messages have this Message-ID (diff)
From: Haren Myneni <haren@linux.vnet.ibm.com>
To: Colin King <colin.king@canonical.com>
Cc: Haren Myneni <haren@us.ibm.com>,
Herbert Xu <herbert@gondor.apana.org.au>,
"David S . Miller" <davem@davemloft.net>,
Benjamin Herrenschmidt <benh@kernel.crashing.org>,
Paul Mackerras <paulus@samba.org>,
Michael Ellerman <mpe@ellerman.id.au>,
linux-crypto@vger.kernel.org, linuxppc-dev@lists.ozlabs.org,
kernel-janitors@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH][V2] crypto/nx: fix spelling mistake: "availavle" -> "available"
Date: Tue, 14 Nov 2017 10:20:03 -0800 [thread overview]
Message-ID: <5A0B33D3.4010707@linux.vnet.ibm.com> (raw)
In-Reply-To: <20171114143217.21456-1-colin.king@canonical.com>
Sorry for my mistake. Thanks.
Acked-by: Haren Myneni <haren@us.ibm.com>
On 11/14/2017 06:32 AM, Colin King wrote:
> From: Colin Ian King <colin.king@canonical.com>
>
> Trivial fix to spelling mistake in pr_err error message text. Also
> fix spelling mistake in proceeding comment.
>
> Signed-off-by: Colin Ian King <colin.king@canonical.com>
> ---
> drivers/crypto/nx/nx-842-powernv.c | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/crypto/nx/nx-842-powernv.c b/drivers/crypto/nx/nx-842-powernv.c
> index f2246a5abcf6..1e87637c412d 100644
> --- a/drivers/crypto/nx/nx-842-powernv.c
> +++ b/drivers/crypto/nx/nx-842-powernv.c
> @@ -743,8 +743,8 @@ static int nx842_open_percpu_txwins(void)
> }
>
> if (!per_cpu(cpu_txwin, i)) {
> - /* shoudn't happen, Each chip will have NX engine */
> - pr_err("NX engine is not availavle for CPU %d\n", i);
> + /* shouldn't happen, Each chip will have NX engine */
> + pr_err("NX engine is not available for CPU %d\n", i);
> return -EINVAL;
> }
> }
>
next prev parent reply other threads:[~2017-11-14 18:20 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-14 14:32 [PATCH][V2] crypto/nx: fix spelling mistake: "availavle" -> "available" Colin King
2017-11-14 18:20 ` Haren Myneni [this message]
2017-11-14 18:20 ` Haren Myneni
2017-11-14 19:20 ` Gabriel Paubert
2017-11-14 19:20 ` Gabriel Paubert
2017-11-29 6:35 ` Herbert Xu
2017-11-29 6:35 ` 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=5A0B33D3.4010707@linux.vnet.ibm.com \
--to=haren@linux.vnet.ibm.com \
--cc=benh@kernel.crashing.org \
--cc=colin.king@canonical.com \
--cc=davem@davemloft.net \
--cc=haren@us.ibm.com \
--cc=herbert@gondor.apana.org.au \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=mpe@ellerman.id.au \
--cc=paulus@samba.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.