From: Rui Miguel Silva <rui.silva@linaro.org>
To: "Rachit Dhar" <rchtdhr@gmail.com>, "Rui Miguel Silva" <rmfrfs@gmail.com>
Cc: "Johan Hovold" <johan@kernel.org>,
"Alex Elder" <elder@kernel.org>,
"Greg Kroah-Hartman" <gregkh@linuxfoundation.org>,
<greybus-dev@lists.linaro.org>, <linux-staging@lists.linux.dev>,
<linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v3 4/4] staging: greybus: resolved checkpatch checks for light.c
Date: Thu, 05 Feb 2026 09:47:55 +0000 [thread overview]
Message-ID: <DG6XM4KTQQBU.3257ITEZ9ZF19@linaro.com> (raw)
In-Reply-To: <20260204183142.182785-1-rchtdhr@gmail.com>
Hey Rachit,
Thanks for the patch. And the sending corrections along the path.
On Wed Feb 4, 2026 at 6:31 PM WET, Rachit Dhar wrote:
> Added comment to mutex declarations, to resolve checkpatch.pl checks.
>
> Signed-off-by: Rachit Dhar <rchtdhr@gmail.com>
> ---
> drivers/staging/greybus/light.c | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/staging/greybus/light.c b/drivers/staging/greybus/light.c
> index e509fdc715db..1f2faa6d545d 100644
> --- a/drivers/staging/greybus/light.c
> +++ b/drivers/staging/greybus/light.c
> @@ -37,7 +37,7 @@ struct gb_channel {
> bool releasing;
> bool strobe_state;
> bool active;
> - struct mutex lock;
> + struct mutex lock; /* protects gb_channel->active */
> };
>
> struct gb_light {
> @@ -59,7 +59,7 @@ struct gb_lights {
> struct gb_connection *connection;
> u8 lights_count;
> struct gb_light *lights;
> - struct mutex lights_lock;
> + struct mutex lights_lock; /* protects gb_lights->lights */
> };
>
This LGTM.
Acked-by: Rui Miguel Silva <rui.silva@linaro.org>
Cheers,
Rui
> static void gb_lights_channel_free(struct gb_channel *channel);
> --
> 2.43.0
prev parent reply other threads:[~2026-02-05 9:47 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-04 18:31 Rachit Dhar
2026-02-05 9:47 ` Rui Miguel Silva [this message]
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=DG6XM4KTQQBU.3257ITEZ9ZF19@linaro.com \
--to=rui.silva@linaro.org \
--cc=elder@kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=greybus-dev@lists.linaro.org \
--cc=johan@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-staging@lists.linux.dev \
--cc=rchtdhr@gmail.com \
--cc=rmfrfs@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
all inboxes | Powered by JetHome®