From: Greg KH <gregkh@linuxfoundation.org>
To: Marcos Garcia <magazo2005@gmail.com>
Cc: philipp.g.hortmann@gmail.com, dan.carpenter@linaro.org,
karanja99erick@gmail.com, rodrigo.gobbi.7@gmail.com,
linux-staging@lists.linux.dev, linux-kernel@vger.kernel.org
Subject: Re: [PATCH staging] staging: rtl8723bs: replace magic numbers in rtl8723b_InitBeaconParameters()
Date: Tue, 1 Jul 2025 10:02:54 +0200 [thread overview]
Message-ID: <2025070117-poise-busily-bd0d@gregkh> (raw)
In-Reply-To: <20250701074243.1300186-1-magazo2005@gmail.com>
On Tue, Jul 01, 2025 at 09:40:49AM +0200, Marcos Garcia wrote:
>
>
> Replace hardcoded values in rtl8723b_InitBeaconParameters() with defined constants
> TBTT_PROHIBIT_VENDOR_DEFAULT (0x6404) and BCNTCFG_AIFS_MAX (0x660F) for clarity and
> maintainability, addressing the TODO comment in the code.
>
> The values were sourced from the following documentation:
> - REG_TBTT_PROHIBIT (Offset 0x0540): Bits [15:8] = 0x64 (100ms prohibit time, 1ms units),
> Bits [7:0] = 0x04 (2ms margin, 0.5ms units), as per RTL8723BS Datasheet v1.5,
> Section 7.3.1.5 and RTL8723BS Programming Guide, p. 112.
> - REG_BCNTCFG (Offset 0x0510): 0x660F sets max AIFS (0x0F) to prioritize beacon
> transmission, as per RTL8723BS Datasheet v1.5, Section 7.3.1.3.
>
> Hi Dan,
>
> Thank you for your detailed feedback — I truly appreciate it. I tried to contact you
> earlier, but it seems my email didn't reach you. This is my first kernel contribution,
> and I started by addressing TODO comments, thinking they were straightforward. I now
> realize even these changes require deep hardware understanding. I used AI to assist with
> parts of the commit message, but I didn't review it thoroughly enough, and I take full
> responsibility for the vague comments. I could only find limited references to these
> values, and the documentation seems restricted. I apologize for any oversight and
> promise to research more carefully in the future. Thank you for your guidance.
None of this needs to be in the changelog text, please read the
documentation for how to properly submit patches, especially second
version of patches.
thanks,
greg k-h
next prev parent reply other threads:[~2025-07-01 8:02 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-01 7:40 [PATCH staging] staging: rtl8723bs: replace magic numbers in rtl8723b_InitBeaconParameters() Marcos Garcia
2025-07-01 8:02 ` Greg KH [this message]
2025-07-01 8:16 ` Greg KH
2025-07-01 14:10 ` Dan Carpenter
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=2025070117-poise-busily-bd0d@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=dan.carpenter@linaro.org \
--cc=karanja99erick@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-staging@lists.linux.dev \
--cc=magazo2005@gmail.com \
--cc=philipp.g.hortmann@gmail.com \
--cc=rodrigo.gobbi.7@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