From: Dan Carpenter <error27@gmail.com>
To: contectforbusiness@proton.me
Cc: "gregkh@linuxfoundation.org" <gregkh@linuxfoundation.org>,
"rmfrfs@gmail.com" <rmfrfs@gmail.com>,
"johan@kernel.org" <johan@kernel.org>,
"elder@kernel.org" <elder@kernel.org>,
"greybus-dev@lists.linaro.org" <greybus-dev@lists.linaro.org>,
"linux-staging@lists.linux.dev" <linux-staging@lists.linux.dev>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 2/2] staging: greybus: light: add comments to mutex definitions
Date: Wed, 9 Sep 2026 17:46:54 +0300 [thread overview]
Message-ID: <aqFxXt8NJ8bMVUV3@stanley.mountain> (raw)
In-Reply-To: <PqjvDjNm1A3nH3BCu_rlHx6YLIzrr0r8McQL1Xbg5GX6VcF6GW49nKPhkTIcHashk4ktOEARq8_izQ6xyFqeWAliK0JqQ8MMPOrFIXSowcw=@proton.me>
On Fri, Sep 04, 2026 at 05:56:25AM +0000, contectforbusiness@proton.me wrote:
> checkpatch complains about:
>
> CHECK: struct mutex definition without comment
>
> Add short comments describing what each mutex protects.
Is this an AI patch? Why write a short description? That's the
opposite of what I want. I want a complete analysis.
> The
> channel lock protects the channel state and lights_lock protects
> the lights array.
>
> No functional change, just quiets checkpatch.
>
> Signed-off-by: Vaibhav <contectforbusiness@proton.me>
> ---
> 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 cab02b5da..a036fa2a0 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 channel */
This comment is useless and wrong.
I hate this checkpatch warning...
regards,
dan carpenter
prev parent reply other threads:[~2026-09-09 14:53 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-04 5:56 contectforbusiness
2026-09-07 16:26 ` gregkh
2026-09-09 13:34 ` contectforbusiness
2026-09-09 14:46 ` Dan Carpenter [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=aqFxXt8NJ8bMVUV3@stanley.mountain \
--to=error27@gmail.com \
--cc=contectforbusiness@proton.me \
--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=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®