From: Karthikeyan Periyasamy <periyasa@codeaurora.org>
To: ath11k@lists.infradead.org
Cc: Karthikeyan Periyasamy <periyasa@codeaurora.org>
Subject: [PATCH 1/5] ath11k: fix variable name warnings
Date: Tue, 25 Jun 2019 09:43:15 +0530 [thread overview]
Message-ID: <1561435999-28316-1-git-send-email-periyasa@codeaurora.org> (raw)
drivers/net/wireless/ath/ath11k/wmi.h:2728: <BK_Minfree>
drivers/net/wireless/ath/ath11k/wmi.h:2729: <BE_Minfree>
drivers/net/wireless/ath/ath11k/wmi.h:2730: <VI_Minfree>
drivers/net/wireless/ath/ath11k/wmi.h:2731: <VO_Minfree>
drivers/net/wireless/ath/ath11k/wmi.h:2965: <bcn_txPower>
Signed-off-by: Karthikeyan Periyasamy <periyasa@codeaurora.org>
---
drivers/net/wireless/ath/ath11k/wmi.h | 18 +++++++++---------
1 file changed, 9 insertions(+), 9 deletions(-)
diff --git a/drivers/net/wireless/ath/ath11k/wmi.h b/drivers/net/wireless/ath/ath11k/wmi.h
index 4e92bf0..779209a 100644
--- a/drivers/net/wireless/ath/ath11k/wmi.h
+++ b/drivers/net/wireless/ath/ath11k/wmi.h
@@ -2725,10 +2725,10 @@ struct wmi_resource_config {
u32 num_ocb_schedules;
u32 flag1;
u32 smart_ant_cap;
- u32 BK_Minfree;
- u32 BE_Minfree;
- u32 VI_Minfree;
- u32 VO_Minfree;
+ u32 bk_minfree;
+ u32 be_minfree;
+ u32 vi_minfree;
+ u32 vo_minfree;
u32 alloc_frag_desc_for_data_pkt;
u32 num_ns_ext_tuples_cfg;
u32 bpf_instruction_size;
@@ -2962,7 +2962,7 @@ struct wmi_vdev_start_request_cmd {
u32 flags;
struct wmi_ssid ssid;
u32 bcn_tx_rate;
- u32 bcn_txPower;
+ u32 bcn_txpower;
u32 num_noa_descriptors;
u32 disable_hw_ack;
u32 preferred_tx_streams;
@@ -5122,10 +5122,10 @@ struct target_resource_config {
u32 max_frag_entries;
u32 max_peer_ext_stats;
u32 smart_ant_cap;
- u32 BK_Minfree;
- u32 BE_Minfree;
- u32 VI_Minfree;
- u32 VO_Minfree;
+ u32 bk_minfree;
+ u32 be_minfree;
+ u32 vi_minfree;
+ u32 vo_minfree;
u32 rx_batchmode;
u32 tt_support;
u32 atf_config;
--
1.9.1
_______________________________________________
ath11k mailing list
ath11k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath11k
next reply other threads:[~2019-06-25 4:13 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-25 4:13 Karthikeyan Periyasamy [this message]
2019-06-25 4:13 ` [PATCH 2/5] ath11k: avoid unnecessary 'out of memory' message Karthikeyan Periyasamy
2019-06-25 4:13 ` [PATCH 3/5] ath11k: fix space related warnings Karthikeyan Periyasamy
2019-06-25 4:13 ` [PATCH 4/5] ath11k: avoid min() warning Karthikeyan Periyasamy
2019-06-25 4:13 ` [PATCH 5/5] ath11k: fix brace warning Karthikeyan Periyasamy
2019-06-25 14:26 ` [PATCH 1/5] ath11k: fix variable name warnings Kalle Valo
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=1561435999-28316-1-git-send-email-periyasa@codeaurora.org \
--to=periyasa@codeaurora.org \
--cc=ath11k@lists.infradead.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