From: Nikolay Kulikov <nikolayof23@gmail.com>
To: Noah Techoueyres <noahtechoueyres@gmail.com>
Cc: gregkh@linuxfoundation.org, linux-staging@lists.linux.dev,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] staging: rtl8723bs: fix line length checks in rtw_cmd.c
Date: Sun, 10 May 2026 22:18:48 +0300 [thread overview]
Message-ID: <agDaGJ5UKndFUNPY@archlinux> (raw)
In-Reply-To: <20260510032936.2852-1-noahtechoueyres@gmail.com>
On Sat, May 09, 2026 at 11:29:36PM -0400, Noah Techoueyres wrote:
> Fix both block comments and assignment statements that exceed the
> 100-column limit to follow Linux guidelines for readability.
>
> Signed-off-by: Noah Techoueyres <noahtechoueyres@gmail.com>
> ---
> drivers/staging/rtl8723bs/core/rtw_cmd.c | 23 +++++++++++++++++------
> 1 file changed, 17 insertions(+), 6 deletions(-)
>
> diff --git a/drivers/staging/rtl8723bs/core/rtw_cmd.c b/drivers/staging/rtl8723bs/core/rtw_cmd.c
> index c1185c25ed36..a401c856c727 100644
> --- a/drivers/staging/rtl8723bs/core/rtw_cmd.c
> +++ b/drivers/staging/rtl8723bs/core/rtw_cmd.c
> @@ -1117,13 +1117,17 @@ static void collect_traffic_statistics(struct adapter *padapter)
> pdvobjpriv->traffic_stat.rx_drop = padapter->recvpriv.rx_drop;
>
> /* Calculate throughput in last interval */
> - pdvobjpriv->traffic_stat.cur_tx_bytes = pdvobjpriv->traffic_stat.tx_bytes - pdvobjpriv->traffic_stat.last_tx_bytes;
> - pdvobjpriv->traffic_stat.cur_rx_bytes = pdvobjpriv->traffic_stat.rx_bytes - pdvobjpriv->traffic_stat.last_rx_bytes;
> + pdvobjpriv->traffic_stat.cur_tx_bytes =
> + pdvobjpriv->traffic_stat.tx_bytes - pdvobjpriv->traffic_stat.last_tx_bytes;
> + pdvobjpriv->traffic_stat.cur_rx_bytes =
> + pdvobjpriv->traffic_stat.rx_bytes - pdvobjpriv->traffic_stat.last_rx_bytes;
> pdvobjpriv->traffic_stat.last_tx_bytes = pdvobjpriv->traffic_stat.tx_bytes;
> pdvobjpriv->traffic_stat.last_rx_bytes = pdvobjpriv->traffic_stat.rx_bytes;
>
> - pdvobjpriv->traffic_stat.cur_tx_tp = (u32)(pdvobjpriv->traffic_stat.cur_tx_bytes * 8 / 2 / 1024 / 1024);
> - pdvobjpriv->traffic_stat.cur_rx_tp = (u32)(pdvobjpriv->traffic_stat.cur_rx_bytes * 8 / 2 / 1024 / 1024);
> + pdvobjpriv->traffic_stat.cur_tx_tp =
> + (u32)(pdvobjpriv->traffic_stat.cur_tx_bytes * 8 / 2 / 1024 / 1024);
> + pdvobjpriv->traffic_stat.cur_rx_tp =
> + (u32)(pdvobjpriv->traffic_stat.cur_rx_bytes * 8 / 2 / 1024 / 1024);
> }
What about adding an intermediate pointer to traffic_stat?
This will not only reduce the length of the lines, but will also make
the code easier to read.
Thanks,
Nikolay
>
> bool traffic_status_watchdog(struct adapter *padapter, bool from_timer)
> @@ -1743,7 +1747,11 @@ u8 rtw_drvextra_cmd_hdl(struct adapter *padapter, unsigned char *pbuf)
> pdrvextra_cmd = (struct drvextra_cmd_parm *)pbuf;
>
> switch (pdrvextra_cmd->ec_id) {
> - case DYNAMIC_CHK_WK_CID:/* only primary padapter go to this cmd, but execute dynamic_chk_wk_hdl() for two interfaces */
> + case DYNAMIC_CHK_WK_CID:
> + /*
> + * only primary padapter go to this cmd, but execute
> + * dynamic_chk_wk_hdl() for two interfaces
> + */
> dynamic_chk_wk_hdl(padapter);
> break;
> case POWER_SAVING_CTRL_WK_CID:
> @@ -1881,7 +1889,10 @@ void rtw_createbss_cmd_callback(struct adapter *padapter, struct cmd_obj *pcmd)
> _clr_fwstate_(pmlmepriv, _FW_UNDER_LINKING);
>
> spin_unlock_bh(&pmlmepriv->scanned_queue.lock);
> - /* we will set _FW_LINKED when there is one more sat to join us (rtw_stassoc_event_callback) */
> + /*
> + * we will set _FW_LINKED when there is one more sta
> + * to join us (rtw_stassoc_event_callback)
> + */
> }
>
> createbss_cmd_fail:
> --
> 2.53.0
>
prev parent reply other threads:[~2026-05-10 19:18 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-10 3:29 [PATCH] staging: rtl8723bs: fix line length checks in rtw_cmd.c Noah Techoueyres
2026-05-10 19:18 ` Nikolay Kulikov [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=agDaGJ5UKndFUNPY@archlinux \
--to=nikolayof23@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-staging@lists.linux.dev \
--cc=noahtechoueyres@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