From: Kalle Valo <kvalo@qca.qualcomm.com>
To: ath9k-devel@lists.ath9k.org
Subject: [ath9k-devel] [PATCH 2/2] ath10k: rename ath10k_p2p module parameter to p2p
Date: Sat, 04 May 2013 08:38:46 +0300 [thread overview]
Message-ID: <20130504053846.19752.73678.stgit@localhost6.localdomain6> (raw)
In-Reply-To: <20130504053749.19752.97101.stgit@localhost6.localdomain6>
AFAICS there's no need to have the ath10k_ prefix in p2p
kernel module parameter so remove that. The name of
the actual variable in code stays the same, ath10k_p2p.
Signed-off-by: Kalle Valo <kvalo@qca.qualcomm.com>
---
drivers/net/wireless/ath/ath10k/core.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/drivers/net/wireless/ath/ath10k/core.c b/drivers/net/wireless/ath/ath10k/core.c
index d0d8521..5dc02ea 100644
--- a/drivers/net/wireless/ath/ath10k/core.c
+++ b/drivers/net/wireless/ath/ath10k/core.c
@@ -32,10 +32,10 @@ static bool uart_print;
static unsigned int ath10k_p2p;
module_param_named(debug_mask, ath10k_debug_mask, uint, 0644);
module_param(uart_print, bool, 0644);
-module_param(ath10k_p2p, uint, 0644);
+module_param_named(p2p, ath10k_p2p, uint, 0644);
MODULE_PARM_DESC(debug_mask, "Debugging mask");
MODULE_PARM_DESC(uart_print, "Uart target debugging");
-MODULE_PARM_DESC(ath10k_p2p, "Enable ath10k P2P support");
+MODULE_PARM_DESC(p2p, "Enable ath10k P2P support");
static const struct ath10k_hw_params ath10k_hw_params_list[] = {
{
next prev parent reply other threads:[~2013-05-04 5:38 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-04 5:38 [ath9k-devel] [PATCH 0/2] ath10k: module parameter fine tuning Kalle Valo
2013-05-04 5:38 ` [ath9k-devel] [PATCH 1/2] ath10k: rename debug_mask Kalle Valo
2013-05-04 5:38 ` Kalle Valo [this message]
2013-05-07 13:45 ` [ath9k-devel] [PATCH 0/2] ath10k: module parameter fine tuning 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=20130504053846.19752.73678.stgit@localhost6.localdomain6 \
--to=kvalo@qca.qualcomm.com \
--cc=ath9k-devel@lists.ath9k.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