From: Kalle Valo <kvalo@qca.qualcomm.com>
To: <ali@internetdog.org>
Cc: <linux-wireless@vger.kernel.org>, <joe@perches.com>,
<devel@linuxdriverproject.org>, <gregkh@suse.de>,
<error27@gmail.com>
Subject: Re: [PATCH v2 00/23] ath6kl cleaned up driver
Date: Tue, 19 Jul 2011 07:26:44 +0300 [thread overview]
Message-ID: <4E250784.3020005@qca.qualcomm.com> (raw)
In-Reply-To: <20110719042119.GA2988@internetdog.org>
Hi Ali,
On 07/19/2011 07:21 AM, Ali Bahar wrote:
>
> On Sun, Jul 17, 2011 at 01:20:07PM +0300, Kalle Valo wrote:
>> Hello,
>>
>> last May we started working on cleaning up ath6kl driver which is
>> currently in staging. The work has happened in a separate
>> ath6kl-cleanup tree:
>>
>> http://git.kernel.org/?p=linux/kernel/git/kvalo/ath6kl-cleanup.git;a=summary
>>
>> After over 1100 (!) patches we have now reached a state where I would
>> like to start discussing about pushing the driver to the wireless
>> trees and replacing the staging driver.
>
>> Please review and comment. John, please consider taking this driver to
>> wireless-testing.
>
> you seem to have not CCed John on this.
Good point, I missed him but I'm sure he got it anyway through
linux-wireless mailing list. Next time I'll CC him.
Kalle
prev parent reply other threads:[~2011-07-19 4:26 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-17 10:20 [PATCH v2 00/23] ath6kl cleaned up driver Kalle Valo
2011-07-17 10:20 ` [PATCH v2 01/23] ath6kl: add bmi.c Kalle Valo
2011-07-17 10:20 ` [PATCH v2 02/23] ath6kl: add bmi.h Kalle Valo
2011-07-17 10:21 ` [PATCH v2 03/23] ath6kl: add cfg80211.c Kalle Valo
2011-07-17 11:12 ` Johannes Berg
2011-07-17 19:40 ` Kalle Valo
2011-07-17 10:21 ` [PATCH v2 04/23] ath6kl: add cfg80211.h Kalle Valo
2011-07-17 10:21 ` [PATCH v2 05/23] ath6kl: add common.h Kalle Valo
2011-07-17 10:21 ` [PATCH v2 06/23] ath6kl: add core.h Kalle Valo
2011-07-17 10:21 ` [PATCH v2 07/23] ath6kl: add debug.c Kalle Valo
2011-07-17 10:22 ` [PATCH v2 08/23] ath6kl: add debug.h Kalle Valo
2011-07-17 10:22 ` [PATCH v2 09/23] ath6kl: add hif-ops.h Kalle Valo
2011-07-17 10:22 ` [PATCH v2 10/23] ath6kl: add hif.h Kalle Valo
2011-07-17 10:22 ` [PATCH v2 11/23] ath6kl: add htc.c Kalle Valo
2011-07-17 10:22 ` [PATCH v2 12/23] ath6kl: add htc.h Kalle Valo
2011-07-17 10:22 ` [PATCH v2 13/23] ath6kl: add htc_hif.c Kalle Valo
2011-07-17 10:23 ` [PATCH v2 14/23] ath6kl: add htc_hif.h Kalle Valo
2011-07-17 10:23 ` [PATCH v2 15/23] ath6kl: add init.c Kalle Valo
2011-07-17 10:23 ` [PATCH v2 16/23] ath6kl: add main.c Kalle Valo
2011-07-17 10:23 ` [PATCH v2 17/23] ath6kl: add node.c Kalle Valo
2011-07-17 10:23 ` [PATCH v2 18/23] ath6kl: add sdio.c Kalle Valo
2011-07-17 10:24 ` [PATCH v2 19/23] ath6kl: add target.h Kalle Valo
2011-07-17 10:24 ` [PATCH v2 20/23] ath6kl: add txrx.c Kalle Valo
2011-07-17 10:24 ` [PATCH v2 21/23] ath6kl: add wmi.c Kalle Valo
2011-07-17 10:24 ` [PATCH v2 22/23] ath6kl: add wmi.h Kalle Valo
2011-07-17 10:24 ` [PATCH v2 23/23] ath6kl: add Kconfig and Makefile Kalle Valo
2011-07-17 10:57 ` [PATCH v2 00/23] ath6kl cleaned up driver Kalle Valo
2011-07-19 4:21 ` Ali Bahar
2011-07-19 4:26 ` Kalle Valo [this message]
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=4E250784.3020005@qca.qualcomm.com \
--to=kvalo@qca.qualcomm.com \
--cc=ali@internetdog.org \
--cc=devel@linuxdriverproject.org \
--cc=error27@gmail.com \
--cc=gregkh@suse.de \
--cc=joe@perches.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).