mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Rachit Dhar <rchtdhr@gmail.com>
Cc: Viresh Kumar <vireshk@kernel.org>,
	Johan Hovold <johan@kernel.org>, Alex Elder <elder@kernel.org>,
	greybus-dev@lists.linaro.org, linux-staging@lists.linux.dev,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3 1/4] staging: greybus: added comment to mutex declaration in fw-management.c
Date: Sat, 7 Feb 2026 14:38:50 +0100	[thread overview]
Message-ID: <2026020704-velocity-palpitate-afd2@gregkh> (raw)
In-Reply-To: <20260204183003.182728-1-rchtdhr@gmail.com>

On Wed, Feb 04, 2026 at 06:30:03PM +0000, Rachit Dhar wrote:
> Added comment to mutex declaration, to resolve a checkpatch.pl check.
> 
> Signed-off-by: Rachit Dhar <rchtdhr@gmail.com>
> ---
>  drivers/staging/greybus/fw-management.c | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/drivers/staging/greybus/fw-management.c b/drivers/staging/greybus/fw-management.c
> index 152949c23d65..07a0e6b63cf3 100644
> --- a/drivers/staging/greybus/fw-management.c
> +++ b/drivers/staging/greybus/fw-management.c
> @@ -28,7 +28,7 @@ struct fw_mgmt {
>  
>  	/* Common id-map for interface and backend firmware requests */
>  	struct ida		id_map;
> -	struct mutex		mutex;
> +	struct mutex		mutex; /* protects fw_mgmt->disabled, and serializes ioctl */

How do you "know" that this is what it is for?

Fixing this type of checkpatch warning is hard, and requires lots of
documentation and checking.  If you didn't write the code originally, I
wouldn't worry about this type of issue at all, it's best for new code,
not existing code.

thanks,

greg k-h

  reply	other threads:[~2026-02-07 13:38 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-02-04 18:30 Rachit Dhar
2026-02-07 13:38 ` Greg Kroah-Hartman [this message]
2026-02-16  4:52   ` Rachit Dhar

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=2026020704-velocity-palpitate-afd2@gregkh \
    --to=gregkh@linuxfoundation.org \
    --cc=elder@kernel.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=vireshk@kernel.org \
    /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®