From: Greg KH <gregkh@linuxfoundation.org>
To: Rutansh Suthar <rutanshsuthar@gmail.com>
Cc: dan.carpenter@linaro.org, zhaochenguang@kylinos.cn,
linux-staging@lists.linux.dev, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v1] staging: rtl8723bs: fix block comment coding style in rtw_io.c
Date: Wed, 17 Dec 2025 14:00:59 +0100 [thread overview]
Message-ID: <2025121750-smartness-ship-b187@gregkh> (raw)
In-Reply-To: <20251202234318.75104-1-rutanshsuthar@gmail.com>
On Tue, Dec 02, 2025 at 03:43:18PM -0800, Rutansh Suthar wrote:
> Fix block comment alignment and style in rtw_io.c to match kernel
> coding style standards.
>
> No functional changes intended.
>
> Signed-off-by: Rutansh Suthar <rutanshsuthar@gmail.com>
> ---
> drivers/staging/rtl8723bs/core/rtw_io.c | 51 +++++++++++++------------
> 1 file changed, 26 insertions(+), 25 deletions(-)
Does not apply at all to the latest kernel tree :(
prev parent reply other threads:[~2025-12-17 13:01 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-02 23:43 [PATCH v1] staging: rtl8723bs: fix block comment coding style in rtw_io.c Rutansh Suthar
2025-12-17 13:00 ` 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=2025121750-smartness-ship-b187@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=dan.carpenter@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-staging@lists.linux.dev \
--cc=rutanshsuthar@gmail.com \
--cc=zhaochenguang@kylinos.cn \
/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