From: Alison Schofield <amsfield22@gmail.com>
To: Anchal Jain <anchalj109@gmail.com>
Cc: Michael.Hennerich@analog.com, gregkh@linuxfoundation.org,
outreachy-kernel@googlegroups.com
Subject: Re: [Outreachy kernel] [PATCH] staging: iio: gyro: add comment to mutex
Date: Wed, 28 Sep 2016 10:55:05 -0700 [thread overview]
Message-ID: <20160928175504.GA10225@d830.WORKGROUP> (raw)
In-Reply-To: <20160928170708.GA6196@life-desktop>
On Wed, Sep 28, 2016 at 10:37:17PM +0530, Anchal Jain wrote:
> Fix the checkpatch.pl issues:
> CHECK: struct mutes definition without comment
^^spelling
>
> Signed-off-by: Anchal Jain <anchalj109@gmail.com>
Hi Anchal, I'm going to be picky on these, because I sense you
are getting on a roll here and we should establish a pattern.
- see spelling above.
- include driver name in IIO commit paths.
Caveat: if the subdir and driver names get so crazy long that you
can't fit a good commit message, then leave off the subdir.
- tab out the comment instead of space.
- At first I thought tx and rx were kind of terse, but when I scroll
up and see the comment above, it all makes sense.
- I might have said 'protect transfer buffers'
Please update with the minor cleanups and resend to the wider
'CC list as suggested in your previous patch.
alisons
> ---
> drivers/staging/iio/gyro/adis16060_core.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/staging/iio/gyro/adis16060_core.c b/drivers/staging/iio/gyro/adis16060_core.c
> index ab816a2..96230b6 100644
> --- a/drivers/staging/iio/gyro/adis16060_core.c
> +++ b/drivers/staging/iio/gyro/adis16060_core.c
> @@ -33,7 +33,7 @@
> struct adis16060_state {
> struct spi_device *us_w;
> struct spi_device *us_r;
> - struct mutex buf_lock;
> + struct mutex buf_lock; /* protect tx and rx */
>
> u8 buf[3] ____cacheline_aligned;
> };
> --
> 1.9.1
>
> --
> 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 visit https://groups.google.com/d/msgid/outreachy-kernel/20160928170708.GA6196%40life-desktop.
> For more options, visit https://groups.google.com/d/optout.
next prev parent reply other threads:[~2016-09-28 17:55 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-28 17:07 [PATCH] staging: iio: gyro: add comment to mutex Anchal Jain
2016-09-28 17:55 ` Alison Schofield [this message]
2016-09-28 20:41 ` [Outreachy kernel] " Julia Lawall
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=20160928175504.GA10225@d830.WORKGROUP \
--to=amsfield22@gmail.com \
--cc=Michael.Hennerich@analog.com \
--cc=anchalj109@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=outreachy-kernel@googlegroups.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.