From: Kalle Valo <kvalo@qca.qualcomm.com>
To: kvalo@qca.qualcomm.com
Cc: ath6kl-devel@qualcomm.com, linux-wireless@vger.kernel.org
Subject: [PATCH 0/2] ath6kl: firmware API 3 support
Date: Fri, 16 Dec 2011 20:53:20 +0200 [thread overview]
Message-ID: <20111216185200.18442.29650.stgit@localhost6.localdomain6> (raw)
First some refactoring to make it easier to extend the firmware handling
and then a patch adding support for firmware API 3.
---
Kalle Valo (2):
ath6kl: handle firmware names more dynamically
ath6kl: add support for FW API 3
drivers/net/wireless/ath/ath6kl/core.h | 46 +++++++------
drivers/net/wireless/ath/ath6kl/init.c | 113 +++++++++++++++++---------------
drivers/net/wireless/ath/ath6kl/sdio.c | 16 ++---
drivers/net/wireless/ath/ath6kl/usb.c | 5 +
4 files changed, 98 insertions(+), 82 deletions(-)
next reply other threads:[~2011-12-16 18:53 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-16 18:53 Kalle Valo [this message]
2011-12-16 18:53 ` [PATCH 1/2] ath6kl: handle firmware names more dynamically Kalle Valo
2011-12-16 18:53 ` [PATCH 2/2] ath6kl: add support for FW API 3 Kalle Valo
2011-12-23 12:59 ` [PATCH 0/2] ath6kl: firmware API 3 support 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=20111216185200.18442.29650.stgit@localhost6.localdomain6 \
--to=kvalo@qca.qualcomm.com \
--cc=ath6kl-devel@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).