From: Dan Carpenter <dan.carpenter@linaro.org>
To: Zile Xiong <xiongzile99@gmail.com>
Cc: gregkh@linuxfoundation.org, ovidiu.panait.oss@gmail.com,
linux-staging@lists.linux.dev, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] staging: axis-fifo: remove redundant comments for mutex fields
Date: Fri, 20 Mar 2026 12:35:26 +0300 [thread overview]
Message-ID: <ab0U3jlEF-hw9ktp@stanley.mountain> (raw)
In-Reply-To: <20260320044040.21149-1-xiongzile99@gmail.com>
On Fri, Mar 20, 2026 at 12:40:40PM +0800, Zile Xiong wrote:
> Remove redundant comments for read_lock and write_lock, as the
> field names already clearly describe their purpose.
>
> Signed-off-by: Zile Xiong <xiongzile99@gmail.com>
You're not wrong, but this introduces a checkpatch warning so we
can't accept it either.
regards,
dan carpenter
prev parent reply other threads:[~2026-03-20 9:35 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-20 4:40 [PATCH] staging: axis-fifo: remove redundant comments for mutex fields Zile Xiong
2026-03-20 9:35 ` 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=ab0U3jlEF-hw9ktp@stanley.mountain \
--to=dan.carpenter@linaro.org \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-staging@lists.linux.dev \
--cc=ovidiu.panait.oss@gmail.com \
--cc=xiongzile99@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