From: Greg KH <gregkh@linuxfoundation.org>
To: Bramwel Barack <bramwelbarack89@gmail.com>
Cc: linux-staging@lists.linux.dev, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] staging: rtl8723bs: fix line length warnings in os_intfs.c
Date: Tue, 28 Jul 2026 17:54:10 +0200 [thread overview]
Message-ID: <2026072826-cocoa-chance-aa5a@gregkh> (raw)
In-Reply-To: <amjKM_tz7ul0vj40@fedora>
On Tue, Jul 28, 2026 at 06:26:43PM +0300, Bramwel Barack wrote:
> The current formatting standards in the file rtl8723bs violates the
> kernel coding standards of 100 lines.
> Targeted most comments of code while avoiding key functions and comments
> included due to indents.
>
> >From 08a6ba8dd59504c030c0e6c9f9459a53436d32eb Mon Sep 17 00:00:00 2001
> From: Bramwel Barack <bramwelbarack89@gmail.com>
> Date: Tue, 28 Jul 2026 17:50:30 +0300
> Subject: [PATCH] staging: rtl8723bs: fix line length warnings in os_intfs.c
>
> Signed-off-by: Bramwel Barack <bramwelbarack89@gmail.com>
No changelog text? Something went wrong here, perhaps use `b4` to
create and send patches out? Heck, even I've started using it, it
really is a nice workflow to learn.
> ---
> drivers/staging/rtl8723bs/os_dep/os_intfs.c | 37 ++++++++++++++++-----
> 1 file changed, 29 insertions(+), 8 deletions(-)
>
> diff --git a/drivers/staging/rtl8723bs/os_dep/os_intfs.c b/drivers/staging/rtl8723bs/os_dep/os_intfs.c
> index c15056ee207c..c916f6f52253 100644
> --- a/drivers/staging/rtl8723bs/os_dep/os_intfs.c
> +++ b/drivers/staging/rtl8723bs/os_dep/os_intfs.c
> @@ -71,20 +71,36 @@ int rtw_ht_enable = 1;
> * 0x01 means enable 2.4G 40MHz
> */
> static int rtw_bw_mode = 0x01;
> -static int rtw_ampdu_enable = 1;/* for enable tx_ampdu ,0: disable, 0x1:enable (but wifi_spec should be 0), 0x2: force enable (don't care wifi_spec) */
> +static int rtw_ampdu_enable = 1;
> +/* for enable tx_ampdu ,0: disable */
> +/* 0x1:enable (but wifi_spec should be 0) */
> +/* 0x2: force enable (don't care wifi_spec) */
Shouldn't the comment be on the top of the variable?
thanks,
greg k-h
prev parent reply other threads:[~2026-07-28 15:54 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-28 15:26 [PATCH] staging: rtl8723bs: fix line length warnings in os_intfs.c Bramwel Barack
2026-07-28 15:54 ` 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=2026072826-cocoa-chance-aa5a@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=bramwelbarack89@gmail.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