From: Philipp Hortmann <philipp.g.hortmann@gmail.com>
To: Manjae Cho <manjae.cho@samsung.com>, gregkh@linuxfoundation.org
Cc: linux-staging@lists.linux.dev, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] staging: rtl8723bs: Improve clarity of MAR usage
Date: Wed, 31 Jul 2024 21:38:00 +0200 [thread overview]
Message-ID: <8f82f816-b677-4f6d-b381-d25f0bb04521@gmail.com> (raw)
In-Reply-To: <20240731081540.912533-1-manjae.cho@samsung.com>
On 7/31/24 10:15, Manjae Cho wrote:
> This patch improves the readability of the code related to the Multicast
> Address Register (REG_MAR) in the rtl8723bs driver. It adds comments to
> clarify the purpose and offset of the register, making the code more
> self-documenting without introducing new macros.
>
> Signed-off-by: Manjae Cho <manjae.cho@samsung.com>
> ---
>
> v2: Add comments for clarity instead of new macros
>
> drivers/staging/rtl8723bs/hal/sdio_halinit.c | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/staging/rtl8723bs/hal/sdio_halinit.c b/drivers/staging/rtl8723bs/hal/sdio_halinit.c
> index c9cd6578f7f8..535cd439121d 100644
> --- a/drivers/staging/rtl8723bs/hal/sdio_halinit.c
> +++ b/drivers/staging/rtl8723bs/hal/sdio_halinit.c
> @@ -380,8 +380,8 @@ static void _InitWMACSetting(struct adapter *padapter)
> rtw_write32(padapter, REG_RCR, pHalData->ReceiveConfig);
>
> /* Accept all multicast address */
> - rtw_write32(padapter, REG_MAR, 0xFFFFFFFF);
> - rtw_write32(padapter, REG_MAR + 4, 0xFFFFFFFF);
> + rtw_write32(padapter, REG_MAR, 0xFFFFFFFF); /* Offset 0x0620-0x0623 */
> + rtw_write32(padapter, REG_MAR + 4, 0xFFFFFFFF); /* Offset 0x0624-0x0627 */
>
> /* Accept all data frames */
> value16 = 0xFFFF;
Hi Manjae,
may be this is version v2 of this patch with this subject. But the
version is not about the subject. It is about the code change itself.
So I can see that this patch was send in with the following subjects:
[PATCH] Improve MAR register definition and usage for rtl8723
[PATCH v2] staging: rtl8723bs: Improve MAR register definition and usage
[PATCH] staging: rtl8723bs: Improve MAR register definition and usage
[PATCH v2] staging: rtl8723bs: Improve clarity of MAR usage
To me the last patch should be a v4. The next patch you send is the v5.
A change history is expected.
Description from Dan under:
https://staticthinking.wordpress.com/2022/07/27/how-to-send-a-v2-patch/
Thanks for your support.
Bye Philipp
next prev parent reply other threads:[~2024-07-31 19:38 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20240731081603epcas1p1d140964329ddaf9146bacb6bd1111506@epcas1p1.samsung.com>
2024-07-31 8:15 ` [PATCH v2] staging: rtl8723bs: Improve clarity of MAR usage Manjae Cho
2024-07-31 19:38 ` Philipp Hortmann [this message]
2024-07-31 22:56 ` Manjae Cho
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=8f82f816-b677-4f6d-b381-d25f0bb04521@gmail.com \
--to=philipp.g.hortmann@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-staging@lists.linux.dev \
--cc=manjae.cho@samsung.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