From: Dan Carpenter <dan.carpenter@oracle.com>
To: Srishti Sharma <srishtishar@gmail.com>
Cc: devel@driverdev.osuosl.org, gregkh@linuxfoundation.org,
driverdev-devel@linuxdriverproject.org,
linux-kernel@vger.kernel.org, outreachy-kernel@googlegroups.com,
linux-crypto@vger.kernel.org
Subject: Re: [PATCH] Staging: ccree: ssi_cipher.c: Correct spelling mistake.
Date: Wed, 6 Sep 2017 23:59:55 +0300 [thread overview]
Message-ID: <20170906205955.s22ssdslev3o4yiq@mwanda> (raw)
In-Reply-To: <1504725863-8495-1-git-send-email-srishtishar@gmail.com>
On Thu, Sep 07, 2017 at 12:54:23AM +0530, Srishti Sharma wrote:
> Correct spelling of counter in comment .
>
> Signed-off-by: Srishti Sharma <srishtishar@gmail.com>
> ---
> drivers/staging/ccree/ssi_cipher.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/staging/ccree/ssi_cipher.c b/drivers/staging/ccree/ssi_cipher.c
> index 8d31a93..99232b2 100644
> --- a/drivers/staging/ccree/ssi_cipher.c
> +++ b/drivers/staging/ccree/ssi_cipher.c
> @@ -702,7 +702,7 @@ static int ssi_blkcipher_complete(struct device *dev,
>
> ssi_buffer_mgr_unmap_blkcipher_request(dev, req_ctx, ivsize, src, dst);
>
> - /*Set the inflight couter value to local variable*/
> + /*Set the inflight counter value to local variable*/
> inflight_counter = ctx_p->drvdata->inflight_counter;
Sure, but it would be better to just delete the comment. It's obvious.
But really just delete the local inflight_counter variable as well
because that's never used.
regards,
dan carpenter
next prev parent reply other threads:[~2017-09-06 20:59 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-06 19:24 [PATCH] Staging: ccree: ssi_cipher.c: Correct spelling mistake Srishti Sharma
[not found] ` <2b8bde9c-6e84-48c5-ab93-76127f314429@googlegroups.com>
2017-09-06 20:39 ` [Outreachy kernel] " Julia Lawall
2017-09-06 20:59 ` Dan Carpenter [this message]
2017-09-06 21:02 ` Srishti Sharma
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=20170906205955.s22ssdslev3o4yiq@mwanda \
--to=dan.carpenter@oracle.com \
--cc=devel@driverdev.osuosl.org \
--cc=driverdev-devel@linuxdriverproject.org \
--cc=gregkh@linuxfoundation.org \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=outreachy-kernel@googlegroups.com \
--cc=srishtishar@gmail.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