From: "Luis R. Rodriguez" <lrodriguez@atheros.com>
To: linville@tuxdriver.com
Cc: linux-wireless@vger.kernel.org, ath9k-devel@lists.ath9k.org,
"Luis R. Rodriguez" <lrodriguez@atheros.com>
Subject: [PATCH 0/5] ath9k_hw: name fixes and reset fix
Date: Tue, 27 Oct 2009 12:59:32 -0400 [thread overview]
Message-ID: <1256662777-20469-1-git-send-email-lrodriguez@atheros.com> (raw)
John here this series has the name fix plus two more fixes I made
yesterday to get ar9271 to reset the hw properly.
Luis R. Rodriguez (5):
ath9k_hw: move mac name and rf name helpers to hw code
ath9k_hw: distinguish single-chip solutions on initial probe print
ath9k_hw: add AR9271 single chip name mapping
ath9k_hw: correct AR_PHY_SPECTRAL_SCAN register offset
ath9k_hw: remove bogus register write on ath9k_hw_9271_pa_cal()
drivers/net/wireless/ath/ath9k/ahb.c | 10 ++--
drivers/net/wireless/ath/ath9k/calib.c | 2 +-
drivers/net/wireless/ath/ath9k/hw.c | 89 +++++++++++++++++++++++++++++++-
drivers/net/wireless/ath/ath9k/hw.h | 2 +
drivers/net/wireless/ath/ath9k/main.c | 58 ---------------------
drivers/net/wireless/ath/ath9k/pci.c | 10 ++--
drivers/net/wireless/ath/ath9k/phy.h | 16 +++++-
7 files changed, 113 insertions(+), 74 deletions(-)
next reply other threads:[~2009-10-27 16:59 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-27 16:59 Luis R. Rodriguez [this message]
2009-10-27 16:59 ` [PATCH 1/5] ath9k_hw: move mac name and rf name helpers to hw code Luis R. Rodriguez
2009-10-27 16:59 ` [PATCH 2/5] ath9k_hw: distinguish single-chip solutions on initial probe print Luis R. Rodriguez
2009-10-27 16:59 ` [PATCH 3/5] ath9k_hw: add AR9271 single chip name mapping Luis R. Rodriguez
2009-10-27 16:59 ` [PATCH 4/5] ath9k_hw: correct AR_PHY_SPECTRAL_SCAN register offset Luis R. Rodriguez
2009-10-27 16:59 ` [PATCH 5/5] ath9k_hw: remove bogus register write on ath9k_hw_9271_pa_cal() Luis R. Rodriguez
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=1256662777-20469-1-git-send-email-lrodriguez@atheros.com \
--to=lrodriguez@atheros.com \
--cc=ath9k-devel@lists.ath9k.org \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
/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