Linux kernel staging patches
 help / color / mirror / Atom feed
From: Manjae Cho <manjae.cho@samsung.com>
To: gregkh@linuxfoundation.org
Cc: linux-staging@lists.linux.dev, linux-kernel@vger.kernel.org,
	Manjae Cho <manjae.cho@samsung.com>
Subject: [PATCH v2] staging: rtl8723bs: Improve MAR register definition and usage
Date: Wed, 31 Jul 2024 08:10:48 +0900	[thread overview]
Message-ID: <20240730231046.412876-1-manjae.cho@samsung.com> (raw)
In-Reply-To: CGME20240731004335epcas1p382229e79bdaf3f2d48b0f3faa7414ea6@epcas1p3.samsung.com

This patch improves the usage of the MAR register by updating the relevant
macro definitions and ensuring consistent usage across the codebase.

Signed-off-by: Manjae Cho <manjae.cho@samsung.com>
---
v2: Fix line length

 drivers/staging/rtl8723bs/include/hal_com_reg.h | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/drivers/staging/rtl8723bs/include/hal_com_reg.h b/drivers/staging/rtl8723bs/include/hal_com_reg.h
index baf326d53a46..93aa391fa749 100644
--- a/drivers/staging/rtl8723bs/include/hal_com_reg.h
+++ b/drivers/staging/rtl8723bs/include/hal_com_reg.h
@@ -151,8 +151,8 @@
 #define REG_BSSID						0x0618
 #define REG_MAR							0x0620
 
-#define MAR0						REG_MAR		/* Multicast Address Register, Offset 0x0620-0x0623 */
-#define MAR4						(REG_MAR + 4)	/* Multicast Address Register, Offset 0x0624-0x0627 */
+#define MAR0		REG_MAR		/* Multicast Address Register, Offset 0x0620-0x0623 */
+#define MAR4		(REG_MAR + 4)	/* Multicast Address Register, Offset 0x0624-0x0627 */
 
 #define REG_MAC_SPEC_SIFS				0x063A
 /*  20100719 Joseph: Hardware register definition change. (HW datasheet v54) */
-- 
2.25.1


       reply	other threads:[~2024-07-31  0:43 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CGME20240731004335epcas1p382229e79bdaf3f2d48b0f3faa7414ea6@epcas1p3.samsung.com>
2024-07-30 23:10 ` Manjae Cho [this message]
2024-07-31  4:58   ` [PATCH v2] staging: rtl8723bs: Improve MAR register definition and usage Philipp Hortmann

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=20240730231046.412876-1-manjae.cho@samsung.com \
    --to=manjae.cho@samsung.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