From: Dan Carpenter <dan.carpenter@linaro.org>
To: "Jose A. Perez de Azpillaga" <azpijr@gmail.com>
Cc: johan@kernel.org, elder@kernel.org, gregkh@linuxfoundation.org,
greybus-dev@lists.linaro.org, linux-staging@lists.linux.dev,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] staging: greybus: camera: add comment for mutex
Date: Wed, 25 Feb 2026 14:18:03 +0300 [thread overview]
Message-ID: <aZ7aaxEWO_7gaNzY@stanley.mountain> (raw)
In-Reply-To: <20260225110511.107114-1-azpijr@gmail.com>
On Wed, Feb 25, 2026 at 12:05:06PM +0100, Jose A. Perez de Azpillaga wrote:
> diff --git a/drivers/staging/greybus/camera.c b/drivers/staging/greybus/camera.c
> index 62b55bb28408..a6f3637b8871 100644
> --- a/drivers/staging/greybus/camera.c
> +++ b/drivers/staging/greybus/camera.c
> @@ -53,7 +53,7 @@ struct gb_camera {
> struct gb_connection *data_connection;
> u16 data_cport_id;
>
> - struct mutex mutex;
> + struct mutex mutex; /* Protects camera state */
I'm not sure what it means, and looking at how the mutex is used I
don't feel it's accurate either.
To be honest, I rarely love these lock documentation patches... :/
They're often really vague and sometimes seem like just guessing based
on the name.
regards,
dan carpenter
> enum gb_camera_state state;
>
> struct {
next prev parent reply other threads:[~2026-02-25 11:18 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-25 11:05 [PATCH] staging: greybus: camera: add comment for mutex Jose A. Perez de Azpillaga
2026-02-25 11:18 ` Dan Carpenter [this message]
[not found] <DAN_CARPENTERS_MESSAGE_ID>
2026-02-25 11:31 ` Jose A. Perez de Azpillaga
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=aZ7aaxEWO_7gaNzY@stanley.mountain \
--to=dan.carpenter@linaro.org \
--cc=azpijr@gmail.com \
--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 \
/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