From: "John W. Linville" <linville@tuxdriver.com>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: linux-wireless <linux-wireless@vger.kernel.org>
Subject: Re: [PATCH] cfg80211: drop wext channel list if too long
Date: Fri, 13 Mar 2009 10:54:45 -0400 [thread overview]
Message-ID: <20090313145445.GC5551@tuxdriver.com> (raw)
In-Reply-To: <1236882244.25931.5.camel@johannes.local>
On Thu, Mar 12, 2009 at 07:24:04PM +0100, Johannes Berg wrote:
> wext limits the number of channels it can list to 32, we obey
> that limitation but show a partial list which is confusing.
> Thus, when going over the limit, drop the list completely to
> make the users aware that something is wrong and hopefully
> prompt them to use iw instead. We still let iwlist print out
> the total number of available channels.
>
> Signed-off-by: Johannes Berg <johannes@sipsolutions.net>
Will this make wpa_supplicant or Networkmanager barf?
John
--
John W. Linville Someday the world will need a hero, and you
linville@tuxdriver.com might be all we have. Be ready.
next prev parent reply other threads:[~2009-03-13 15:00 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-12 18:24 [PATCH] cfg80211: drop wext channel list if too long Johannes Berg
2009-03-13 14:54 ` John W. Linville [this message]
2009-03-13 17:18 ` Dan Williams
2009-03-14 8:30 ` Johannes Berg
2009-03-16 16:56 ` 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=20090313145445.GC5551@tuxdriver.com \
--to=linville@tuxdriver.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).