From: Larry Finger <larry.finger@lwfinger.net>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: John Linville <linville@tuxdriver.com>, Jiri Benc <jbenc@suse.cz>,
linux-wireless <linux-wireless@vger.kernel.org>
Subject: Re: [PATCH 4/4] mac80211: remove radar stuff
Date: Sat, 11 Aug 2007 12:00:57 -0500 [thread overview]
Message-ID: <46BDEB49.2070703@lwfinger.net> (raw)
In-Reply-To: <1186820267.5363.1.camel@johannes.berg>
Johannes Berg wrote:
> On Fri, 2007-08-10 at 22:18 -0500, Larry Finger wrote:
>> Johannes Berg wrote:
>>> Unused in drivers, userspace and mac80211.
>>>
>>> Signed-off-by: Johannes Berg <johannes@sipsolutions.net>
>>> ---
>> Won't 802.11a drivers need this? If so, does it hurt to leave it in for now?
>
> Absolutely correct, they probably will. None of the ones we have,
> however, actually uses it, and it uses the management interface we're
> trying to get rid of for the notification. The same function should
> probably be added back to mac80211 or cfg80211 once somebody actually
> wants it, but do the notification
> 1) with well-defined arguments (explanation for the two args anyone?)
> 2) via nl80211
>
> It doesn't really "hurt" but I'm trying to actually remove the master
> interface now and I'm almost there, so this code is in my way.
OK, thanks for the explanation.
Larry
prev parent reply other threads:[~2007-08-11 17:01 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-10 22:05 [PATCH 0/4] remove a few more unused constants Johannes Berg
2007-08-10 22:05 ` [PATCH 1/4] mac80211: remove ieee80211_msg_wep_frame_unknown_key Johannes Berg
2007-08-10 22:05 ` [PATCH 2/4] mac80211: dont send frames from unassociated stations up Johannes Berg
2007-08-10 22:05 ` [PATCH 3/4] mac80211: remove ieee80211_msg_key_threshold_notification Johannes Berg
2007-08-10 22:05 ` [PATCH 4/4] mac80211: remove radar stuff Johannes Berg
2007-08-11 3:18 ` Larry Finger
2007-08-11 8:17 ` Johannes Berg
2007-08-11 17:00 ` Larry Finger [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=46BDEB49.2070703@lwfinger.net \
--to=larry.finger@lwfinger.net \
--cc=jbenc@suse.cz \
--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).