From: Ben Greear <greearb@candelatech.com>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: linux-wireless@vger.kernel.org
Subject: Re: Missing config_hw() in ieee80211_ibss_join?
Date: Mon, 31 Jan 2011 10:45:45 -0800 [thread overview]
Message-ID: <4D470359.6050902@candelatech.com> (raw)
In-Reply-To: <1296499385.3812.40.camel@jlt3.sipsolutions.net>
On 01/31/2011 10:43 AM, Johannes Berg wrote:
> On Mon, 2011-01-31 at 10:29 -0800, Ben Greear wrote:
>> The method ieee80211_ibss_join can change the operating channel,
>> but I don't see anywhere that it calls config_hw to flush the
>> changes into the kernel.
>>
>> Should we add such a call?
>
> I don't think so -- it doesn't actually really join until it has scanned
> first etc.?
Ok, good enough for me. I don't think this will cause any problems
with my scan-on-channel logic, but it looked a bit strange while
I was auditing the oper-channel related code.
Thanks,
Ben
--
Ben Greear <greearb@candelatech.com>
Candela Technologies Inc http://www.candelatech.com
prev parent reply other threads:[~2011-01-31 18:45 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-31 18:29 Missing config_hw() in ieee80211_ibss_join? Ben Greear
2011-01-31 18:43 ` Johannes Berg
2011-01-31 18:45 ` Ben Greear [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=4D470359.6050902@candelatech.com \
--to=greearb@candelatech.com \
--cc=johannes@sipsolutions.net \
--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).