From: Dan Carpenter <dan.carpenter@linaro.org>
To: Rahul Joshi <rj5547884@gmail.com>
Cc: dtwlin@gmail.com, 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: uart: add comments to locks and fix alignment
Date: Mon, 16 Mar 2026 10:20:31 +0300 [thread overview]
Message-ID: <abevP7wQGicCe9nZ@stanley.mountain> (raw)
In-Reply-To: <20260311184104.499201-1-rj5547884@gmail.com>
On Thu, Mar 12, 2026 at 12:11:04AM +0530, Rahul Joshi wrote:
> The spinlock_t and struct mutex members in struct gb_tty lack
> comments describing what they protect, which is required by the
> kernel coding style.
>
> Also fix the alignment of the wait_for_completion_timeout() call
> in gb_uart_wait_for_all_credits() to match the open parenthesis.
>
> Signed-off-by: Rahul Joshi <rj5547884@gmail.com>
> ---
> drivers/staging/greybus/uart.c | 8 ++++----
> 1 file changed, 4 insertions(+), 4 deletions(-)
>
> diff --git a/drivers/staging/greybus/uart.c b/drivers/staging/greybus/uart.c
> index 7d060b4cd33d..52a84a68049c 100644
> --- a/drivers/staging/greybus/uart.c
> +++ b/drivers/staging/greybus/uart.c
> @@ -50,12 +50,12 @@ struct gb_tty {
> unsigned int minor;
> unsigned char clocal;
> bool disconnected;
> - spinlock_t read_lock;
> - spinlock_t write_lock;
> + spinlock_t read_lock; /* protects iocount and oldcount */
> + spinlock_t write_lock; /* protects write_fifo and credits */
https://lore.kernel.org/all/aaFdxqxEUzZFVIqQ@stanley.mountain/
How on earth could you have come up with the exact same words here
that someone else did? It feels like too large of a coincidence.
regards,
dan carpenter
prev parent reply other threads:[~2026-03-16 7:20 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-11 18:41 [PATCH] staging: greybus: uart: add comments to locks and fix alignment Rahul Joshi
2026-03-12 5:12 ` Greg KH
2026-03-16 7:20 ` 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=abevP7wQGicCe9nZ@stanley.mountain \
--to=dan.carpenter@linaro.org \
--cc=dtwlin@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 \
--cc=rj5547884@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