From: Steve Lin <steven.lin1@broadcom.com>
To: Colin King <colin.king@canonical.com>
Cc: Herbert Xu <herbert@gondor.apana.org.au>,
"David S . Miller" <davem@davemloft.net>,
Rob Rice <rob.rice@broadcom.com>,
Corentin LABBE <clabbe.montjoie@gmail.com>,
linux-crypto@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] crypto: brcm: fix spelling mistake: "fallbck" -> "fallback"
Date: Mon, 5 Jun 2017 10:10:48 -0400 [thread overview]
Message-ID: <CA+Jmh7F0oWL44==Xsy6HY_kabVQQNcefh3Q8S0mH5mHhRyD1ag@mail.gmail.com> (raw)
In-Reply-To: <20170604182920.26389-1-colin.king@canonical.com>
On Sun, Jun 4, 2017 at 2:29 PM, Colin King <colin.king@canonical.com> wrote:
> From: Colin Ian King <colin.king@canonical.com>
>
> Trivial fix to spelling mistake in flow_log message
>
> Signed-off-by: Colin Ian King <colin.king@canonical.com>
Good catch, thanks!
Reviewed-by: Steve Lin <steven.lin1@broadcom.com>
> ---
> drivers/crypto/bcm/cipher.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/crypto/bcm/cipher.c b/drivers/crypto/bcm/cipher.c
> index 61393dc70b0b..9cfd36c1bcb6 100644
> --- a/drivers/crypto/bcm/cipher.c
> +++ b/drivers/crypto/bcm/cipher.c
> @@ -2639,7 +2639,7 @@ static int aead_need_fallback(struct aead_request *req)
> (spu->spu_type == SPU_TYPE_SPUM) &&
> (ctx->digestsize != 8) && (ctx->digestsize != 12) &&
> (ctx->digestsize != 16)) {
> - flow_log("%s() AES CCM needs fallbck for digest size %d\n",
> + flow_log("%s() AES CCM needs fallback for digest size %d\n",
> __func__, ctx->digestsize);
> return 1;
> }
> --
> 2.11.0
>
next prev parent reply other threads:[~2017-06-05 14:10 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-04 18:29 [PATCH] crypto: brcm: fix spelling mistake: "fallbck" -> "fallback" Colin King
2017-06-05 14:10 ` Steve Lin [this message]
2017-06-19 6:43 ` 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='CA+Jmh7F0oWL44==Xsy6HY_kabVQQNcefh3Q8S0mH5mHhRyD1ag@mail.gmail.com' \
--to=steven.lin1@broadcom.com \
--cc=clabbe.montjoie@gmail.com \
--cc=colin.king@canonical.com \
--cc=davem@davemloft.net \
--cc=herbert@gondor.apana.org.au \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rob.rice@broadcom.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.