From: Julia Lawall <julia.lawall@lip6.fr>
To: Srishti Sharma <srishtishar@gmail.com>
Cc: outreachy-kernel <outreachy-kernel@googlegroups.com>,
gregkh@linuxfoundation.org, gilad@benyossef.com,
linux-crypto@vger.kernel.org,
driverdev-devel@linuxdriverproject.org,
devel@driverdev.osuosl.org, linux-kernel@vger.kernel.org
Subject: Re: [Outreachy kernel] Re: [PATCH] Staging: ccree: ssi_cipher.c: Correct spelling mistake.
Date: Wed, 6 Sep 2017 22:39:54 +0200 (CEST) [thread overview]
Message-ID: <alpine.DEB.2.20.1709062235350.2984@hadrien> (raw)
In-Reply-To: <2b8bde9c-6e84-48c5-ab93-76127f314429@googlegroups.com>
[-- Attachment #1: Type: text/plain, Size: 2383 bytes --]
On Wed, 6 Sep 2017, Srishti Sharma wrote:
>
>
> On Thursday, September 7, 2017 at 12:54:49 AM UTC+5:30, 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;
> /*Decrease the inflight counter*/
> if (ctx_p->flow_mode == BYPASS &&
> ctx_p->drvdata->inflight_counter > 0)
> --
> 2.7.4
>
>
> Hey,
>
> Can I say , /* store the value of inflight_counter variable from driver
> private data context to a local variable */ , to make it more
> comprehensible ?
I think it could be a bit of overkill. The "driver private data context"
part can be seen from a quick glance at the code. Also, it could be good
to bring out the purpose rather than just what the code does. So "save
inflight_counter in a a local variable" could be better, because it
focuses on the idea of saving some information for later use. Good job on
figuring out the formatting problem.
julia
>
> Regards,
> Srishti
>
> --
> You received this message because you are subscribed to the Google Groups
> "outreachy-kernel" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to outreachy-kernel+unsubscribe@googlegroups.com.
> To post to this group, send email to outreachy-kernel@googlegroups.com.
> To view this discussion on the web visithttps://groups.google.com/d/msgid/outreachy-kernel/2b8bde9c-6e84-48c5-ab93-
> 76127f314429%40googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>
>
next prev parent reply other threads:[~2017-09-06 20:39 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 ` Julia Lawall [this message]
2017-09-06 20:59 ` Dan Carpenter
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=alpine.DEB.2.20.1709062235350.2984@hadrien \
--to=julia.lawall@lip6.fr \
--cc=devel@driverdev.osuosl.org \
--cc=driverdev-devel@linuxdriverproject.org \
--cc=gilad@benyossef.com \
--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