From: kbuild test robot <lkp@intel.com>
To: John Crispin <john@phrozen.org>,
Johannes Berg <johannes@sipsolutions.net>,
Kalle Valo <kvalo@codeaurora.org>
Cc: kbuild-all@lists.01.org, linux-wireless@vger.kernel.org,
ath11k@lists.infradead.org, Miles Hu <milehu@codeaurora.org>,
John Crispin <john@phrozen.org>
Subject: [RFC PATCH] ath11k: ath11k_mac_get_tx_mcs_map() can be static
Date: Fri, 1 May 2020 10:14:03 +0800 [thread overview]
Message-ID: <20200501021403.GA34224@2ec9c934b904> (raw)
In-Reply-To: <20200429145708.25992-3-john@phrozen.org>
Signed-off-by: kbuild test robot <lkp@intel.com>
---
mac.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/net/wireless/ath/ath11k/mac.c b/drivers/net/wireless/ath/ath11k/mac.c
index ad05409783c05..c8acdc1e33353 100644
--- a/drivers/net/wireless/ath/ath11k/mac.c
+++ b/drivers/net/wireless/ath/ath11k/mac.c
@@ -5285,7 +5285,7 @@ ath11k_mac_has_single_legacy_rate(struct ath11k *ar,
return num_rates == 1;
}
-u16 ath11k_mac_get_tx_mcs_map(const struct ieee80211_sta_he_cap *he_cap)
+static u16 ath11k_mac_get_tx_mcs_map(const struct ieee80211_sta_he_cap *he_cap)
{
if (he_cap->he_cap_elem.phy_cap_info[0] &
IEEE80211_HE_PHY_CAP0_CHANNEL_WIDTH_SET_80PLUS80_MHZ_IN_5G)
next prev parent reply other threads:[~2020-05-01 2:14 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-29 14:57 [PATCH V3 1/3] nl80211: add support for setting fixed HE rate/gi/ltf John Crispin
2020-04-29 14:57 ` [PATCH V3 2/3] mac80211: " John Crispin
2020-04-29 14:57 ` [PATCH V3 3/3] ath11k: " John Crispin
2020-04-30 8:46 ` Kalle Valo
2020-05-01 2:14 ` kbuild test robot
2020-05-01 2:14 ` kbuild test robot [this message]
2020-04-30 22:38 ` [PATCH V3 1/3] nl80211: " 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=20200501021403.GA34224@2ec9c934b904 \
--to=lkp@intel.com \
--cc=ath11k@lists.infradead.org \
--cc=johannes@sipsolutions.net \
--cc=john@phrozen.org \
--cc=kbuild-all@lists.01.org \
--cc=kvalo@codeaurora.org \
--cc=linux-wireless@vger.kernel.org \
--cc=milehu@codeaurora.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).