From: Dan Carpenter <error27@gmail.com>
To: Anantha Krishnan <ananthanr.off@gmail.com>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
linux-staging@lists.linux.dev, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] staging: rtl8723bs: replace magic number in InitBeaconParameters
Date: Sat, 11 Jul 2026 09:42:34 +0300 [thread overview]
Message-ID: <alHl2nsrGPQE-7sN@stanley.mountain> (raw)
In-Reply-To: <20260711063901.30828-2-ananthanr.off@gmail.com>
On Sat, Jul 11, 2026 at 12:09:02PM +0530, Anantha Krishnan wrote:
> Per the bitfield comment in hal_com_reg.h, REG_TBTT_PROHIBIT packs
> a "setup" time in bits 3:0 and a "hold" time in bits 19:8. The
> rtw_write16() call here only writes the low 16 bits of that
> register, covering the full setup field and the low byte of the
> hold field.
>
> Replace the magic number 0x6404 with two named constants
> representing these fields.
>
> No functional change.
>
> Bit-field positions are documented in the comment above
> REG_TBTT_PROHIBIT in drivers/staging/rtl8723bs/include/hal_com_reg.h.
>
> Signed-off-by: Anantha Krishnan <ananthanr.off@gmail.com>
> ---
> v2: Use full name in Signed-off-by and document the source of the
> bitfield values (comment above REG_TBTT_PROHIBIT in hal_com_reg.h)
> per Greg's review.
Please wait 24 hours between resends. Otherwise it feels like we're
holding your hand while you write code. It's overwhelming for
reviewers.
https://staticthinking.wordpress.com/2022/07/27/how-to-send-a-v2-patch/
regards,
dan carpenter
prev parent reply other threads:[~2026-07-11 6:42 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-11 2:40 [PATCH] staging: rtl8723bs: replace magic number in InitBeaconParameters Ananthan
2026-07-11 5:11 ` Greg Kroah-Hartman
2026-07-11 6:22 ` [PATCH v2] " Anantha Krishnan
2026-07-11 6:29 ` Greg Kroah-Hartman
2026-07-11 6:41 ` Dan Carpenter
2026-07-11 6:39 ` Anantha Krishnan
2026-07-11 6:42 ` 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=alHl2nsrGPQE-7sN@stanley.mountain \
--to=error27@gmail.com \
--cc=ananthanr.off@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox