From: kbuild test robot <lkp@intel.com>
To: Shreeya Patel <shreeya.patel23498@gmail.com>
Cc: kbuild-all@01.org, gregkh@linuxfoundation.org,
devel@driverdev.osuosl.org, linux-kernel@vger.kernel.org,
Shreeya Patel <shreeya.patel23498@gmail.com>
Subject: [RFC PATCH] Staging: rtl8723bs: initinterrupt8723bsdio() can be static
Date: Tue, 19 Dec 2017 22:29:49 +0800 [thread overview]
Message-ID: <20171219142949.GA2975@intel11> (raw)
In-Reply-To: <1edacdb32a029727128d2339e13ae04c1e3013a7.1513501505.git.shreeya.patel23498@gmail.com>
Fixes: 8642fab9ea22 ("Staging: rtl8723bs: Change names to conform to the kernel code")
Signed-off-by: Fengguang Wu <fengguang.wu@intel.com>
---
sdio_ops.c | 8 ++++----
1 file changed, 4 insertions(+), 4 deletions(-)
diff --git a/drivers/staging/rtl8723bs/hal/sdio_ops.c b/drivers/staging/rtl8723bs/hal/sdio_ops.c
index 00b20c0..7f3dbe1 100644
--- a/drivers/staging/rtl8723bs/hal/sdio_ops.c
+++ b/drivers/staging/rtl8723bs/hal/sdio_ops.c
@@ -778,7 +778,7 @@ static s32 ReadInterrupt8723BSdio(struct adapter *adapter, u32 *phisr)
/* */
/* Created by Roger, 2011.02.11. */
/* */
-void initinterrupt8723bsdio(struct adapter *adapter)
+static void initinterrupt8723bsdio(struct adapter *adapter)
{
struct hal_com_data *haldata;
@@ -812,7 +812,7 @@ void initinterrupt8723bsdio(struct adapter *adapter)
/* */
/* Created by Roger, 2011.08.03. */
/* */
-void initsysinterrupt8723bsdio(struct adapter *adapter)
+static void initsysinterrupt8723bsdio(struct adapter *adapter)
{
struct hal_com_data *haldata;
@@ -870,7 +870,7 @@ void clearinterrupt8723bsdio(struct adapter *adapter)
/* */
/* Created by Roger, 2011.02.11. */
/* */
-void enable_interrupt8723bsdio(struct adapter *adapter)
+static void enable_interrupt8723bsdio(struct adapter *adapter)
{
struct hal_com_data *haldata;
__le32 himr;
@@ -922,7 +922,7 @@ void enable_interrupt8723bsdio(struct adapter *adapter)
/* */
/* Created by Roger, 2011.02.11. */
/* */
-void disable_interrupt8723bsdio(struct adapter *adapter)
+static void disable_interrupt8723bsdio(struct adapter *adapter)
{
__le32 himr;
next prev parent reply other threads:[~2017-12-19 14:30 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-17 9:35 [PATCH 0/4] Remove checkpatch warnings Shreeya Patel
2017-12-17 9:37 ` [PATCH 1/4] Staging: rtl8723bs: Replace true with x and false with !x Shreeya Patel
2017-12-17 9:45 ` Joe Perches
2017-12-17 9:51 ` Shreeya Patel
2017-12-17 9:39 ` [PATCH 2/4] Staging: rtl8723bs: Change names to conform to the kernel code Shreeya Patel
2017-12-19 14:29 ` kbuild test robot [this message]
2017-12-17 9:40 ` [PATCH 3/4] Staging: rtl8723bs: Change condition to assignment Shreeya Patel
2017-12-17 9:42 ` [PATCH 4/4] Staging: rtl8723bs: Use !x instead of NULL comparison Shreeya Patel
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=20171219142949.GA2975@intel11 \
--to=lkp@intel.com \
--cc=devel@driverdev.osuosl.org \
--cc=gregkh@linuxfoundation.org \
--cc=kbuild-all@01.org \
--cc=linux-kernel@vger.kernel.org \
--cc=shreeya.patel23498@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