From: Sujith Manoharan <sujith@msujith.org>
To: linux-wireless@vger.kernel.org
Cc: ath9k-devel@qca.qualcomm.com
Subject: [PATCH 0/6] ath9k patches
Date: Mon, 19 Jan 2015 07:43:12 +0530 [thread overview]
Message-ID: <1421633598-4488-1-git-send-email-sujith@msujith.org> (raw)
From: Sujith Manoharan <c_manoha@qca.qualcomm.com>
ath9k patches for -next.
Sujith Manoharan (6):
ath9k: Update QCA953x initvals
ath9k: Update AR955x initvals
ath9k: Add a macro to identify PCOEM chips
ath9k: Fix manual peak calibration initialization
ath9k: Set correct peak detect threshold
ath9k: Enable manual peak detect calibration
drivers/net/wireless/ath/ath9k/ar9003_calib.c | 61 +++++++++++++++++-----
drivers/net/wireless/ath/ath9k/ar953x_initvals.h | 4 +-
.../net/wireless/ath/ath9k/ar955x_1p0_initvals.h | 4 +-
drivers/net/wireless/ath/ath9k/reg.h | 3 ++
4 files changed, 55 insertions(+), 17 deletions(-)
--
2.2.2
next reply other threads:[~2015-01-19 2:10 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-19 2:13 Sujith Manoharan [this message]
2015-01-19 2:13 ` [PATCH 1/6] ath9k: Update QCA953x initvals Sujith Manoharan
2015-01-19 2:13 ` [PATCH 2/6] ath9k: Update AR955x initvals Sujith Manoharan
2015-01-19 2:13 ` [PATCH 3/6] ath9k: Add a macro to identify PCOEM chips Sujith Manoharan
2015-01-28 12:10 ` Sujith Manoharan
2015-01-28 12:15 ` Kalle Valo
2015-01-28 12:26 ` Sujith Manoharan
2015-01-28 12:59 ` Kalle Valo
2015-01-28 13:10 ` Sujith Manoharan
2015-01-19 2:13 ` [PATCH 4/6] ath9k: Fix manual peak calibration initialization Sujith Manoharan
2015-01-19 2:13 ` [PATCH 5/6] ath9k: Set correct peak detect threshold Sujith Manoharan
2015-01-19 2:13 ` [PATCH 6/6] ath9k: Enable manual peak detect calibration Sujith Manoharan
-- strict thread matches above, loose matches on Subject: below --
2015-03-01 6:23 [PATCH 0/6] ath9k patches Sujith Manoharan
2015-02-02 12:51 Sujith Manoharan
2015-02-06 6:41 ` Kalle Valo
2014-11-11 7:07 Sujith Manoharan
2014-10-06 5:49 Sujith Manoharan
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=1421633598-4488-1-git-send-email-sujith@msujith.org \
--to=sujith@msujith.org \
--cc=ath9k-devel@qca.qualcomm.com \
--cc=linux-wireless@vger.kernel.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).