From: Johannes Berg <johannes@sipsolutions.net>
To: Ben Greear <greearb@candelatech.com>
Cc: "linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Subject: Re: Replacement for local->hw.conf.channel
Date: Thu, 04 Jul 2013 09:27:50 +0200 [thread overview]
Message-ID: <1372922870.8235.0.camel@jlt4.sipsolutions.net> (raw)
In-Reply-To: <51D4BB56.9070401@candelatech.com> (sfid-20130704_020129_998241_BE6D0EF6)
On Wed, 2013-07-03 at 17:01 -0700, Ben Greear wrote:
> I'm trying to port some patches forward to 3.10....
>
> I am trying to find the current channel for a radio. Since
> hw.conf.channel no longer exists, what is the best way to
> go about this?
Well there's hw.conf.chandef.chan now I think, but that can be NULL and
generic mac80211 code must not use it. There's no single current channel
any more, you want vif->chanctx or so.
johannes
next prev parent reply other threads:[~2013-07-04 7:28 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-04 0:01 Replacement for local->hw.conf.channel Ben Greear
2013-07-04 7:27 ` Johannes Berg [this message]
2013-07-08 18:20 ` Ben Greear
2013-07-08 18:31 ` Johannes Berg
2013-07-08 18:47 ` Ben Greear
2013-07-09 14:35 ` Johannes Berg
2013-07-09 16:32 ` Ben Greear
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=1372922870.8235.0.camel@jlt4.sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=greearb@candelatech.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).