From: Dan Carpenter <dan.carpenter@linaro.org>
To: Shubham Chakraborty <chakrabortyshubham66@gmail.com>
Cc: David Lin <dtwlin@gmail.com>, Johan Hovold <johan@kernel.org>,
Alex Elder <elder@kernel.org>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
greybus-dev@lists.linaro.org, linux-staging@lists.linux.dev,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/2] staging: greybus: uart: fix style issues
Date: Thu, 26 Feb 2026 10:59:19 +0300 [thread overview]
Message-ID: <aZ_9V7cldGzWNDrb@stanley.mountain> (raw)
In-Reply-To: <20260225183836.20434-1-chakrabortyshubham66@gmail.com>
On Thu, Feb 26, 2026 at 12:08:35AM +0530, Shubham Chakraborty wrote:
> Fix checkpatch.pl warnings by adding comments to mutex and spinlocks,
> and fixing alignment to match open parenthesis.
>
> Signed-off-by: Shubham Chakraborty <chakrabortyshubham66@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..1d2c4ef70865 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 read operations */
This is really vague, but I wouldn't say it was accurate.
> + spinlock_t write_lock; /* protects write operations */
Also really vague. What does "operations" mean in this context?
But word "write" is correct at least.
> struct async_icount iocount;
> struct async_icount oldcount;
> wait_queue_head_t wioctl;
> - struct mutex mutex;
> + struct mutex mutex; /* serializes port operations */
This comment is doesn't really add any value.
regards,
dan carpenter
next prev parent reply other threads:[~2026-02-26 7:59 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-25 18:38 [PATCH 1/2] staging: greybus: uart: fix style issues Shubham Chakraborty
2026-02-25 18:38 ` [PATCH 2/2] staging: greybus: uart: convert to XArray Shubham Chakraborty
2026-02-25 18:47 ` Greg Kroah-Hartman
2026-02-26 18:25 ` Shubham Chakraborty
2026-02-25 18:43 ` [PATCH 1/2] staging: greybus: uart: fix style issues Greg Kroah-Hartman
2026-02-26 7:59 ` Dan Carpenter [this message]
2026-02-26 17:58 ` Shubham Chakraborty
2026-02-27 6:52 ` [PATCH v2] staging: greybus: uart: add descriptive lock comments Shubham Chakraborty
2026-02-27 9:03 ` Dan Carpenter
2026-02-27 15:48 ` [PATCH v2] staging: greybus: uart: improve " Shubham Chakraborty
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=aZ_9V7cldGzWNDrb@stanley.mountain \
--to=dan.carpenter@linaro.org \
--cc=chakrabortyshubham66@gmail.com \
--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 \
/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