From: Keith Teeple <keithrteeple@gmail.com>
To: gregkh@linuxfoundation.org
Cc: linux-staging@lists.linux.dev, linux-kernel@vger.kernel.org,
s9430399@naver.com, andriy.shevchenko@intel.com,
Keith Teeple <keithrteeple@gmail.com>
Subject: [PATCH] staging: rtl8723bs: split chained assignment in xmit_linux.c
Date: Wed, 25 Feb 2026 19:10:19 -0500 [thread overview]
Message-ID: <20260226001019.1100684-1-keithrteeple@gmail.com> (raw)
checkpatch reports that multiple assignments should be avoided.
Split the chained assignment into two separate statements.
Signed-off-by: Keith Teeple <keithrteeple@gmail.com>
---
drivers/staging/rtl8723bs/os_dep/xmit_linux.c | 8 ++++----
1 file changed, 4 insertions(+), 4 deletions(-)
diff --git a/drivers/staging/rtl8723bs/os_dep/xmit_linux.c b/drivers/staging/rtl8723bs/os_dep/xmit_linux.c
index 0be3143fffe5..62243ab5fcd4 100644
--- a/drivers/staging/rtl8723bs/os_dep/xmit_linux.c
+++ b/drivers/staging/rtl8723bs/os_dep/xmit_linux.c
@@ -6,7 +6,6 @@
******************************************************************************/
#include <drv_types.h>
-
uint rtw_remainder_len(struct pkt_file *pfile)
{
return (pfile->buf_len - ((SIZE_PTR)(pfile->cur_addr) - (SIZE_PTR)(pfile->buf_start)));
@@ -15,9 +14,10 @@ uint rtw_remainder_len(struct pkt_file *pfile)
void _rtw_open_pktfile(struct sk_buff *pktptr, struct pkt_file *pfile)
{
pfile->pkt = pktptr;
- pfile->cur_addr = pfile->buf_start = pktptr->data;
- pfile->pkt_len = pfile->buf_len = pktptr->len;
-
+ pfile->buf_start = pktptr->data;
+ pfile->cur_addr = pfile->buf_start;
+ pfile->buf_len = pktptr->len;
+ pfile->pkt_len = pfile->buf_len;
pfile->cur_buffer = pfile->buf_start;
}
--
2.53.0
next reply other threads:[~2026-02-26 0:10 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-26 0:10 Keith Teeple [this message]
2026-02-26 1:41 ` [PATCH] staging: rtl8723bs: split chained assignment in xmit_linux.c Greg KH
2026-02-26 7:20 ` Dan Carpenter
2026-02-26 7:59 ` Andy Shevchenko
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=20260226001019.1100684-1-keithrteeple@gmail.com \
--to=keithrteeple@gmail.com \
--cc=andriy.shevchenko@intel.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-staging@lists.linux.dev \
--cc=s9430399@naver.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