From: Bruno Randolf <br1@einfach.org>
To: Brian Prodoehl <bprodoehl@gmail.com>
Cc: johannes@sipsolutions.net, linville@tuxdriver.com,
linux-wireless@vger.kernel.org
Subject: Re: [PATCH] cfg80211: Extend channel to frequency mapping for 802.11j
Date: Sat, 8 Jan 2011 12:43:56 +0900 [thread overview]
Message-ID: <201101081243.56629.br1@einfach.org> (raw)
In-Reply-To: <AANLkTimesMqYthXLSU2RBF=9=5bDXv3QtnOZapCjCquG@mail.gmail.com>
On Friday 07 January 2011 21:53:25 Brian Prodoehl wrote:
> > Do all drivers still build with this patch? I applied the previous
> > RFC version of this patch to a late-December cut of compat-wireless,
> > and had to touch the receive-handling code in a half-dozen or so
> > drivers due to the API changes.
I have to confess, I didn't check the drivers. Just tested with ath5k. Before
this gets merged we have to fix all drivers which use these functions, true. I
will try to do that next week...
> Ah, I see. All the driver changes I needed were because
> ieee80211_channel_to_frequency() changed with the RFC patch, and this
> patch keeps ieee80211_channel_to_frequency() the same. Good stuff.
Uh? This patch also changes ieee80211_channel_to_frequency(). Bad stuff. ;)
bruno
next prev parent reply other threads:[~2011-01-08 3:44 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-07 5:26 [PATCH] cfg80211: Extend channel to frequency mapping for 802.11j Bruno Randolf
2011-01-07 11:43 ` Johannes Berg
2011-01-07 12:45 ` Brian Prodoehl
2011-01-07 12:53 ` Brian Prodoehl
2011-01-08 3:43 ` Bruno Randolf [this message]
2011-01-08 13:08 ` Brian Prodoehl
2011-01-11 9:17 ` Bruno Randolf
2011-01-11 12:18 ` Johannes Berg
2011-01-11 13:16 ` Brian Prodoehl
2011-01-11 15:09 ` Dan Williams
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=201101081243.56629.br1@einfach.org \
--to=br1@einfach.org \
--cc=bprodoehl@gmail.com \
--cc=johannes@sipsolutions.net \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.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).