public inbox for linux-staging@lists.linux.dev
 help / color / mirror / Atom feed
From: Linus Probert <linus.probert@gmail.com>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: linux-staging@lists.linux.dev, linux-kernel@vger.kernel.org,
	Linus Probert <linus.probert@gmail.com>
Subject: [PATCH 2/8] staging: rtl8723bs: add function definition arg names to rtw_btcoex.h
Date: Mon, 27 Apr 2026 19:38:51 +0200	[thread overview]
Message-ID: <20260427173857.585742-3-linus.probert@gmail.com> (raw)
In-Reply-To: <20260427173857.585742-1-linus.probert@gmail.com>

Adds function definition argument names to rtw_btcoex.h in order to
conform to kernel code style. This eliminates warnings generated by
checkpatch.pl.

In all cases it's the 'struct adapter *' argument which has been given
the name 'padapter'. This matches the names used in the implementations
of these functions.

Signed-off-by: Linus Probert <linus.probert@gmail.com>
---
 drivers/staging/rtl8723bs/include/rtw_btcoex.h | 10 +++++-----
 1 file changed, 5 insertions(+), 5 deletions(-)

diff --git a/drivers/staging/rtl8723bs/include/rtw_btcoex.h b/drivers/staging/rtl8723bs/include/rtw_btcoex.h
index 5554118bbe36..df939b20867b 100644
--- a/drivers/staging/rtl8723bs/include/rtw_btcoex.h
+++ b/drivers/staging/rtl8723bs/include/rtw_btcoex.h
@@ -14,14 +14,14 @@
 #define	PACKET_ARP				2
 #define	PACKET_EAPOL			3
 
-void rtw_btcoex_MediaStatusNotify(struct adapter *, u8 mediaStatus);
-void rtw_btcoex_HaltNotify(struct adapter *);
+void rtw_btcoex_MediaStatusNotify(struct adapter *padapter, u8 mediaStatus);
+void rtw_btcoex_HaltNotify(struct adapter *padapter);
 
 /*  ================================================== */
 /*  Below Functions are called by BT-Coex */
 /*  ================================================== */
-void rtw_btcoex_RejectApAggregatedPacket(struct adapter *, u8 enable);
-void rtw_btcoex_LPS_Enter(struct adapter *);
-void rtw_btcoex_LPS_Leave(struct adapter *);
+void rtw_btcoex_RejectApAggregatedPacket(struct adapter *padapter, u8 enable);
+void rtw_btcoex_LPS_Enter(struct adapter *padapter);
+void rtw_btcoex_LPS_Leave(struct adapter *padapter);
 
 #endif /*  __RTW_BTCOEX_H__ */
-- 
2.54.0


  parent reply	other threads:[~2026-04-27 17:39 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-04-27 17:38 [PATCH 0/8] staging: rtl8723bs: remove warnings in rtw_btcoex.h Linus Probert
2026-04-27 17:38 ` [PATCH 1/8] staging: rtl8723bs: remove blank line " Linus Probert
2026-04-27 17:38 ` Linus Probert [this message]
2026-04-27 17:38 ` [PATCH 3/8] staging: rtl8723bs: rename rtw_btcoex_MediaStatusNotify() Linus Probert
2026-04-27 17:38 ` [PATCH 4/8] staging: rtl8723bs: rename rtw_btcoex_media_status_notify definition arg Linus Probert
2026-04-27 17:38 ` [PATCH 5/8] staging: rtl8723bs: rtw_btcoex_HaltNotify() -> rtw_btcoex_halt_notify() Linus Probert
2026-04-27 17:38 ` [PATCH 6/8] staging: rtl8723bs: rename rtw_btcoex_RejectApAggregatedPacket() Linus Probert
2026-04-27 17:38 ` [PATCH 7/8] staging: rtl8723bs: rtw_btcoex_LPS_Enter() -> rtw_btcoex_lps_enter() Linus Probert
2026-04-27 17:38 ` [PATCH 8/8] staging: rtl8723bs: rename rtw_btcoex_LPS_Leave to rtw_btcoex_lps_leave Linus Probert

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=20260427173857.585742-3-linus.probert@gmail.com \
    --to=linus.probert@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