From: kbuild test robot <lkp@intel.com>
To: kbuild-all@lists.01.org
Subject: [RFC PATCH] rtw88: 8723d: rtw8723d_pwr_track() can be static
Date: Tue, 12 May 2020 03:07:31 +0800 [thread overview]
Message-ID: <20200511190731.GA8959@75ebaf9685ab> (raw)
In-Reply-To: <20200507042151.15634-10-yhchuang@realtek.com>
[-- Attachment #1: Type: text/plain, Size: 718 bytes --]
Signed-off-by: kbuild test robot <lkp@intel.com>
---
rtw8723d.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/net/wireless/realtek/rtw88/rtw8723d.c b/drivers/net/wireless/realtek/rtw88/rtw8723d.c
index 400364aec393f..b517af417e0e4 100644
--- a/drivers/net/wireless/realtek/rtw88/rtw8723d.c
+++ b/drivers/net/wireless/realtek/rtw88/rtw8723d.c
@@ -1896,7 +1896,7 @@ static void rtw8723d_phy_pwrtrack(struct rtw_dev *rtwdev)
rtw8723d_phy_calibration(rtwdev);
}
-void rtw8723d_pwr_track(struct rtw_dev *rtwdev)
+static void rtw8723d_pwr_track(struct rtw_dev *rtwdev)
{
struct rtw_efuse *efuse = &rtwdev->efuse;
struct rtw_dm_info *dm_info = &rtwdev->dm_info;
WARNING: multiple messages have this Message-ID (diff)
From: kbuild test robot <lkp@intel.com>
To: yhchuang@realtek.com, kvalo@codeaurora.org
Cc: kbuild-all@lists.01.org, linux-wireless@vger.kernel.org,
pkshih@realtek.com, bigeasy@linutronix.de
Subject: [RFC PATCH] rtw88: 8723d: rtw8723d_pwr_track() can be static
Date: Tue, 12 May 2020 03:07:31 +0800 [thread overview]
Message-ID: <20200511190731.GA8959@75ebaf9685ab> (raw)
In-Reply-To: <20200507042151.15634-10-yhchuang@realtek.com>
Signed-off-by: kbuild test robot <lkp@intel.com>
---
rtw8723d.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/net/wireless/realtek/rtw88/rtw8723d.c b/drivers/net/wireless/realtek/rtw88/rtw8723d.c
index 400364aec393f..b517af417e0e4 100644
--- a/drivers/net/wireless/realtek/rtw88/rtw8723d.c
+++ b/drivers/net/wireless/realtek/rtw88/rtw8723d.c
@@ -1896,7 +1896,7 @@ static void rtw8723d_phy_pwrtrack(struct rtw_dev *rtwdev)
rtw8723d_phy_calibration(rtwdev);
}
-void rtw8723d_pwr_track(struct rtw_dev *rtwdev)
+static void rtw8723d_pwr_track(struct rtw_dev *rtwdev)
{
struct rtw_efuse *efuse = &rtwdev->efuse;
struct rtw_dm_info *dm_info = &rtwdev->dm_info;
next prev parent reply other threads:[~2020-05-11 19:07 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-07 4:21 [PATCH v2 0/9] rtw88: 8723d: Add RF calibration and coex yhchuang
2020-05-07 4:21 ` [PATCH v2 1/9] rtw88: 8723d: Add LC calibration yhchuang
2020-05-12 8:49 ` Kalle Valo
2020-05-07 4:21 ` [PATCH v2 2/9] rtw88: 8723d: add IQ calibration yhchuang
2020-05-07 4:21 ` [PATCH v2 3/9] rtw88: 8723d: Add power tracking yhchuang
2020-05-07 4:21 ` [PATCH v2 4/9] rtw88: 8723d: Add shutdown callback to disable BT USB suspend yhchuang
2020-05-07 4:21 ` [PATCH v2 5/9] rtw88: 8723d: implement flush queue yhchuang
2020-05-07 4:21 ` [PATCH v2 6/9] rtw88: 8723d: set ltecoex register address in chip_info yhchuang
2020-05-07 4:21 ` [PATCH v2 7/9] rtw88: 8723d: Add coex support yhchuang
2020-05-07 4:21 ` [PATCH v2 8/9] rtw88: fill zeros to words 0x06 and 0x07 of security cam entry yhchuang
2020-05-07 4:21 ` [PATCH v2 9/9] rtw88: 8723d: Add 8723DE to Kconfig and Makefile yhchuang
2020-05-11 19:07 ` kbuild test robot
2020-05-11 19:07 ` kbuild test robot
2020-05-11 19:07 ` kbuild test robot [this message]
2020-05-11 19:07 ` [RFC PATCH] rtw88: 8723d: rtw8723d_pwr_track() can be static kbuild test robot
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=20200511190731.GA8959@75ebaf9685ab \
--to=lkp@intel.com \
--cc=kbuild-all@lists.01.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.