From: Joe Perches <joe@perches.com>
To: Pascal Van Leeuwen <pvanleeuwen@verimatrix.com>,
Colin King <colin.king@canonical.com>,
Antoine Tenart <antoine.tenart@bootlin.com>,
Herbert Xu <herbert@gondor.apana.org.au>,
"David S . Miller" <davem@davemloft.net>,
"linux-crypto@vger.kernel.org" <linux-crypto@vger.kernel.org>
Cc: "kernel-janitors@vger.kernel.org"
<kernel-janitors@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH][next] crypto: inside-secure: fix spelling mistake "algorithmn" -> "algorithm"
Date: Tue, 08 Oct 2019 01:28:45 -0700 [thread overview]
Message-ID: <f7fada8a8afce542e5ac08f804df8d5c8d8a726b.camel@perches.com> (raw)
In-Reply-To: <MN2PR20MB29735A64971670E9CE56821ECA9A0@MN2PR20MB2973.namprd20.prod.outlook.com>
On Tue, 2019-10-08 at 08:15 +0000, Pascal Van Leeuwen wrote:
> > There is a spelling mistake in a dev_err message. Fix it.
[]
> > diff --git a/drivers/crypto/inside-secure/safexcel_cipher.c b/drivers/crypto/inside-
[]
> > @@ -437,7 +437,7 @@ static int safexcel_aead_setkey(struct crypto_aead *ctfm, const u8 *key,
> > goto badkey;
> > break;
> > default:
> > - dev_err(priv->dev, "aead: unsupported hash algorithmn");
> > + dev_err(priv->dev, "aead: unsupported hash algorithm");
> > goto badkey;
> > }
[]
> Actually, the typing error is well spotted, but the fix is not correct.
> What actually happened here is that a \ got accidentally deleted,
> there should have been a "\n" at the end of the line ...
Other missing newlines in the same file:
---
drivers/crypto/inside-secure/safexcel_cipher.c | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/drivers/crypto/inside-secure/safexcel_cipher.c b/drivers/crypto/inside-secure/safexcel_cipher.c
index cecc56073337..47fec8a0a4e1 100644
--- a/drivers/crypto/inside-secure/safexcel_cipher.c
+++ b/drivers/crypto/inside-secure/safexcel_cipher.c
@@ -695,21 +695,21 @@ static int safexcel_send_req(struct crypto_async_request *base, int ring,
sreq->nr_dst = sreq->nr_src;
if (unlikely((totlen_src || totlen_dst) &&
(sreq->nr_src <= 0))) {
- dev_err(priv->dev, "In-place buffer not large enough (need %d bytes)!",
+ dev_err(priv->dev, "In-place buffer not large enough (need %d bytes)!\n",
max(totlen_src, totlen_dst));
return -EINVAL;
}
dma_map_sg(priv->dev, src, sreq->nr_src, DMA_BIDIRECTIONAL);
} else {
if (unlikely(totlen_src && (sreq->nr_src <= 0))) {
- dev_err(priv->dev, "Source buffer not large enough (need %d bytes)!",
+ dev_err(priv->dev, "Source buffer not large enough (need %d bytes)!\n",
totlen_src);
return -EINVAL;
}
dma_map_sg(priv->dev, src, sreq->nr_src, DMA_TO_DEVICE);
if (unlikely(totlen_dst && (sreq->nr_dst <= 0))) {
- dev_err(priv->dev, "Dest buffer not large enough (need %d bytes)!",
+ dev_err(priv->dev, "Dest buffer not large enough (need %d bytes)!\n",
totlen_dst);
dma_unmap_sg(priv->dev, src, sreq->nr_src,
DMA_TO_DEVICE);
next prev parent reply other threads:[~2019-10-08 8:28 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-08 8:14 [PATCH][next] crypto: inside-secure: fix spelling mistake "algorithmn" -> "algorithm" Colin King
2019-10-08 8:15 ` Pascal Van Leeuwen
2019-10-08 8:28 ` Joe Perches [this message]
2019-10-08 8:33 ` Pascal Van Leeuwen
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=f7fada8a8afce542e5ac08f804df8d5c8d8a726b.camel@perches.com \
--to=joe@perches.com \
--cc=antoine.tenart@bootlin.com \
--cc=colin.king@canonical.com \
--cc=davem@davemloft.net \
--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=pvanleeuwen@verimatrix.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox