From: Dan Carpenter <dan.carpenter@linaro.org>
To: ashirvadm04@gmail.com
Cc: gregkh@linuxfoundation.org, philipp.g.hortmann@gmail.com,
sayyad.abid16@gmail.com, linux-staging@lists.linux.dev,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] staging: rtl8723bs: Replace magic numbers in rtl8723b_InitBeaconParameters
Date: Thu, 31 Jul 2025 19:05:32 +0300 [thread overview]
Message-ID: <8c350c13-3e6d-45cf-b9d2-2e8df07b6dd2@suswa.mountain> (raw)
In-Reply-To: <20250729141224.16013-1-ashirvadm04@gmail.com>
On Tue, Jul 29, 2025 at 07:42:10PM +0530, ashirvadm04@gmail.com wrote:
> From: Ashirvad Mohanty <ashirvadm04@gmail.com>
>
> Replace magic numbers 0x6404 and 0x660F in rtl8723b_InitBeaconParameters
> with macros TBTT_PROHIBIT_TIME_8723B and BCN_AIFS_CFG_8723B, respectively,
> defined in rtl8723b_hal.h.
I don't really think these names add any information. The number is
related to TIME but no one really knows how it works. Someone posted
a theory about it, but it turned out that was just AI hallucination.
The spec they quoted was real but the sub section was fake.
The 8723B is the name of the driver, but without the "s" for some
reason. It's just words but with no meaning. It's a map to nowhere.
It's a waste of time. I would say that there is also an element where
these names are a bit misleading because the BCN_AIFS_CFG_8723B is
really specific and the name suggests it's more of a generally config
button.
Just leave it as-is. I would suggest that you could delete the TODO,
but it's good practice to just learn to accept that we can't fix
everything.
regards,
dan carpenter
prev parent reply other threads:[~2025-07-31 16:05 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-29 14:12 ashirvadm04
2025-07-31 16:05 ` 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=8c350c13-3e6d-45cf-b9d2-2e8df07b6dd2@suswa.mountain \
--to=dan.carpenter@linaro.org \
--cc=ashirvadm04@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-staging@lists.linux.dev \
--cc=philipp.g.hortmann@gmail.com \
--cc=sayyad.abid16@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
all inboxes | Powered by JetHome®