From: "Ethan Tidmore" <ethantidmore06@gmail.com>
To: "Tan Kai Zhe" <kaizhetan@yahoo.com>, <gregkh@linuxfoundation.org>
Cc: <linux-staging@lists.linux.dev>, <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] staging: rtl8723bs: remove unnecessary blank lines in rtw_io.c
Date: Fri, 06 Feb 2026 12:45:38 -0600 [thread overview]
Message-ID: <DG83ODWLEUH4.3USTRFB2ZE9EW@gmail.com> (raw)
In-Reply-To: <20260206001833.16857-1-kaizhetan@yahoo.com>
On Thu Feb 5, 2026 at 6:18 PM CST, Tan Kai Zhe wrote:
> Adhere to Linux kernel coding style.
>
> Reported by checkpatch:
>
> CHECK: Blank lines aren't necessary before a close brace '}'
>
> Signed-off-by: Tan Kai Zhe <kaizhetan@yahoo.com>
Looks good to me.
Reviewed-by: Ethan Tidmore <ethantidmore06@gmail.com>
ET
prev parent reply other threads:[~2026-02-06 18:45 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20260206001833.16857-1-kaizhetan.ref@yahoo.com>
2026-02-06 0:18 ` [PATCH] staging: rtl8723bs: remove unnecessary blank lines in rtw_io.c Tan Kai Zhe
2026-02-06 18:45 ` Ethan Tidmore [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=DG83ODWLEUH4.3USTRFB2ZE9EW@gmail.com \
--to=ethantidmore06@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=kaizhetan@yahoo.com \
--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