From: Dan Carpenter <dan.carpenter@linaro.org>
To: Artur Stupa <arthur.stupa@gmail.com>
Cc: gregkh@linuxfoundation.org, linux-staging@lists.linux.dev,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v4 1/2] staging: rtl8723bs: core: fix block comment style issues
Date: Mon, 24 Nov 2025 10:58:17 +0300 [thread overview]
Message-ID: <aSQQGULOM-V4smT6@stanley.mountain> (raw)
In-Reply-To: <20251121224143.33701-1-arthur.stupa@gmail.com>
On Fri, Nov 21, 2025 at 02:41:34PM -0800, Artur Stupa wrote:
> Fix the following checkpatch warnings for block comments:
> * Block comments should align the * on each line
> * Block comments use * on subsequent lines
> * Block comments use a trailing */ on a separate line
>
> No functional changes.
>
> Signed-off-by: Artur Stupa <arthur.stupa@gmail.com>
> ---
> Changes in v4:
> * Documented changes between patch versions.
>
> Changes in v3:
> * Deleted ************* lines in comments.
> * Moved dead commented-out code deletion to patch 2/2.
>
> Changes in v2:
> * Fixed "trailing */" checkpatch warnings.
> * Deleted dead commented-out code in rtw_wlan_util.c.
LGTM.
Reviewed-by: Dan Carpenter <dan.carpenter@linaro.org>
regards,
dan carpenter
prev parent reply other threads:[~2025-11-24 7:58 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-19 6:26 [PATCH] staging: rtl8723bs: core: fix block comment style issues Artur Stupa
2025-11-19 11:36 ` Dan Carpenter
2025-11-20 0:29 ` [PATCH v2] " Artur Stupa
2025-11-20 7:22 ` Dan Carpenter
2025-11-20 20:30 ` [PATCH v3 1/2] " Artur Stupa
2025-11-20 20:30 ` [PATCH v3 2/2] staging: rtl8723bs: core: delete commented-out code Artur Stupa
2025-11-21 6:59 ` [PATCH v3 1/2] staging: rtl8723bs: core: fix block comment style issues Greg KH
2025-11-21 22:41 ` [PATCH v4 " Artur Stupa
2025-11-21 22:41 ` [PATCH v4 2/2] staging: rtl8723bs: core: delete commented-out code Artur Stupa
2025-11-24 7:58 ` 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=aSQQGULOM-V4smT6@stanley.mountain \
--to=dan.carpenter@linaro.org \
--cc=arthur.stupa@gmail.com \
--cc=gregkh@linuxfoundation.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.