From: Greg KH <gregkh@linuxfoundation.org>
To: Rahul Joshi <rj5547884@gmail.com>
Cc: rmfrfs@gmail.com, johan@kernel.org, elder@kernel.org,
greybus-dev@lists.linaro.org, linux-staging@lists.linux.dev,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] staging: greybus: gpio: add comment to mutex definition
Date: Wed, 18 Mar 2026 16:30:41 +0100 [thread overview]
Message-ID: <2026031856-dormitory-chamber-91d5@gregkh> (raw)
In-Reply-To: <20260311175334.464391-1-rj5547884@gmail.com>
On Wed, Mar 11, 2026 at 11:23:34PM +0530, Rahul Joshi wrote:
> The irq_lock mutex is missing a comment describing what it protects,
> which is required by kernel coding style. Add a comment clarifying
> that it serializes IRQ bus lock/unlock operations used to defer and
> sync pending IRQ type and mask changes to hardware.
>
> Signed-off-by: Rahul Joshi <rj5547884@gmail.com>
> ---
> drivers/staging/greybus/gpio.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/staging/greybus/gpio.c b/drivers/staging/greybus/gpio.c
> index 12185f7a982c..89c15b804b2a 100644
> --- a/drivers/staging/greybus/gpio.c
> +++ b/drivers/staging/greybus/gpio.c
> @@ -39,7 +39,7 @@ struct gb_gpio_controller {
>
> struct gpio_chip chip;
> struct irq_chip irqc;
> - struct mutex irq_lock;
> + struct mutex irq_lock; /* protects irq bus operations */
What is a "irq bus"? This comment feels odd to me :(
thanks,
greg k-h
prev parent reply other threads:[~2026-03-18 15:30 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-11 17:53 [PATCH] staging: greybus: gpio: add comment to mutex definition Rahul Joshi
2026-03-18 15:30 ` Greg KH [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=2026031856-dormitory-chamber-91d5@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=rj5547884@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