From: Felix Fietkau <nbd@openwrt.org>
To: linux-wireless <linux-wireless@vger.kernel.org>
Cc: "Luis R. Rodriguez" <lrodriguez@atheros.com>,
"John W. Linville" <linville@tuxdriver.com>
Subject: Re: [PATCH] ath9k: fix channel flag / regd issues with multiple cards
Date: Fri, 01 Oct 2010 01:37:19 +0200 [thread overview]
Message-ID: <4CA51F2F.70701@openwrt.org> (raw)
In-Reply-To: <4CA5180D.3010702@openwrt.org>
On 2010-10-01 1:06 AM, Felix Fietkau wrote:
> Since the regulatory code touches the channel array, it needs to be
> copied for each device instance. That way the original channel array
> can also be made const.
>
> Signed-off-by: Felix Fietkau <nbd@openwrt.org>
> Cc: stable@kernel.org [all]
Hmm, don't merge this one just yet. Seems that this may not be the cause
for the weird multi-card regd issues after all, since the code looks
like that part should be properly locked, even for multiple wiphys
sharing the same channel list.
- Felix
next prev parent reply other threads:[~2010-09-30 23:37 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-30 23:06 [PATCH] ath9k: fix channel flag / regd issues with multiple cards Felix Fietkau
2010-09-30 23:37 ` Felix Fietkau [this message]
2010-10-01 14:51 ` Felix Fietkau
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=4CA51F2F.70701@openwrt.org \
--to=nbd@openwrt.org \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=lrodriguez@atheros.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;
as well as URLs for NNTP newsgroup(s).