From: Vasanthakumar Thiagarajan <vthiagar@qca.qualcomm.com>
To: Kalle Valo <kvalo@qca.qualcomm.com>
Cc: <linux-wireless@vger.kernel.org>, <ath6kl-devel@qualcomm.com>
Subject: Re: [PATCH V3 1/5] ath6kl: Group wiphy initialization into ath6kl_cfg80211_init()
Date: Thu, 1 Mar 2012 13:37:52 +0530 [thread overview]
Message-ID: <4F4F2E58.7070302@qca.qualcomm.com> (raw)
In-Reply-To: <4F4F2030.9080805@qca.qualcomm.com>
On Thursday 01 March 2012 12:37 PM, Kalle Valo wrote:
> On 03/01/2012 08:32 AM, Kalle Valo wrote:
>> On 02/28/2012 04:50 PM, Vasanthakumar Thiagarajan wrote:
>>> There are some code which initializes various wiphy members
>>> left outside ath6kl_cfg80211_init(), in ath6kl_core_init().
>>> Move them into a single palce.
>>>
>>> Signed-off-by: Vasanthakumar Thiagarajan<vthiagar@qca.qualcomm.com>
>>
>> Thanks, all five patches applied.
>
> There's an issue and I think these patches might cause it. Earlier (with
> commit 9289a8a8e2) my ath6kl device was always wlan0:
I never noticed any such issues, sure i'll review it once again. Thanks
for reporting this.
Vasanth
prev parent reply other threads:[~2012-03-01 8:08 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-28 14:50 [PATCH V3 1/5] ath6kl: Group wiphy initialization into ath6kl_cfg80211_init() Vasanthakumar Thiagarajan
2012-02-28 14:50 ` [PATCH V3 2/5] ath6kl: Initialize netdev hw_features for every interface Vasanthakumar Thiagarajan
2012-02-28 14:50 ` [PATCH V3 3/5] ath6kl: Refactor ath6kl_wmi_control_rx() Vasanthakumar Thiagarajan
2012-02-28 14:50 ` [PATCH V3 4/5] ath6kl: Skip vif index validation in ath6kl_rx() for wmi events Vasanthakumar Thiagarajan
2012-02-28 14:50 ` [PATCH V3 5/5] ath6kl: Defer wiphy and netdev registration till the end of ath6kl_core_init() Vasanthakumar Thiagarajan
2012-03-01 6:32 ` [PATCH V3 1/5] ath6kl: Group wiphy initialization into ath6kl_cfg80211_init() Kalle Valo
2012-03-01 7:07 ` Kalle Valo
2012-03-01 8:07 ` Vasanthakumar Thiagarajan [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=4F4F2E58.7070302@qca.qualcomm.com \
--to=vthiagar@qca.qualcomm.com \
--cc=ath6kl-devel@qualcomm.com \
--cc=kvalo@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).