From: Mukesh Ojha <mojha@codeaurora.org>
To: "Colin King" <colin.king@canonical.com>,
"Horia Geantă" <horia.geanta@nxp.com>,
"Aymen Sghaier" <aymen.sghaier@nxp.com>,
"Herbert Xu" <herbert@gondor.apana.org.au>,
"David S . Miller" <davem@davemloft.net>,
linux-crypto@vger.kernel.org
Cc: kernel-janitors@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] crypto: caam: fix spelling mistake "cannote" -> "cannot"
Date: Tue, 16 Apr 2019 12:26:28 +0530 [thread overview]
Message-ID: <cd43bdfe-2748-ec47-3ceb-4da84f67cd89@codeaurora.org> (raw)
In-Reply-To: <20190415124021.4659-1-colin.king@canonical.com>
On 4/15/2019 6:10 PM, Colin King wrote:
> From: Colin Ian King <colin.king@canonical.com>
>
> There is a spelling mistake in an error message in the qi_error_list
> array. Fix this.
>
> Signed-off-by: Colin Ian King <colin.king@canonical.com>
Reviewed-by: Mukesh Ojha <mojha@codeaurora.org>
Cheers,
-Mukesh
> ---
> drivers/crypto/caam/error.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/crypto/caam/error.c b/drivers/crypto/caam/error.c
> index 21a70fd32f5d..a4129a35a330 100644
> --- a/drivers/crypto/caam/error.c
> +++ b/drivers/crypto/caam/error.c
> @@ -138,7 +138,7 @@ static const struct {
> { 0x46, "Annotation length exceeds offset (reuse mode)"},
> { 0x48, "Annotation output enabled but ASA limited by ASAR (reuse mode)"},
> { 0x49, "Data offset correction exceeds input frame data length (reuse mode)"},
> - { 0x4B, "Annotation output enabled but ASA cannote be expanded (frame list)"},
> + { 0x4B, "Annotation output enabled but ASA cannot be expanded (frame list)"},
> { 0x51, "Unsupported IF reuse mode"},
> { 0x52, "Unsupported FL use mode"},
> { 0x53, "Unsupported RJD use mode"},
next prev parent reply other threads:[~2019-04-16 6:58 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-15 12:40 [PATCH] crypto: caam: fix spelling mistake "cannote" -> "cannot" Colin King
2019-04-16 6:56 ` Mukesh Ojha [this message]
2019-04-25 7:50 ` 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=cd43bdfe-2748-ec47-3ceb-4da84f67cd89@codeaurora.org \
--to=mojha@codeaurora.org \
--cc=aymen.sghaier@nxp.com \
--cc=colin.king@canonical.com \
--cc=davem@davemloft.net \
--cc=herbert@gondor.apana.org.au \
--cc=horia.geanta@nxp.com \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).