From: "John W. Linville" <linville@tuxdriver.com>
To: Dan Williams <dcbw@redhat.com>
Cc: netdev@vger.kernel.org, Zhu Yi <yi.zhu@intel.com>,
James Ketrenos <jketreno@linux.intel.com>
Subject: Re: [patch] net/ieee80211: report hidden ESSIDs as zero-length, not "<hidden>"
Date: Wed, 12 Apr 2006 17:04:25 -0400 [thread overview]
Message-ID: <20060412210416.GF12788@tuxdriver.com> (raw)
In-Reply-To: <1143215843.3417.16.camel@localhost.localdomain>
On Fri, Mar 24, 2006 at 10:57:22AM -0500, Dan Williams wrote:
> <hidden> this is something that ieee80211 does that's completely wrong.
> Drivers need to report the _exact_ ESSID from the air in their scan
> results. It's up to the user space app to deal with ESSID length of 0.
What is the outcome of this? Did we get agreement on a patch?
John
--
John W. Linville
linville@tuxdriver.com
parent reply other threads:[~2006-04-12 21:05 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <1143215843.3417.16.camel@localhost.localdomain>]
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=20060412210416.GF12788@tuxdriver.com \
--to=linville@tuxdriver.com \
--cc=dcbw@redhat.com \
--cc=jketreno@linux.intel.com \
--cc=netdev@vger.kernel.org \
--cc=yi.zhu@intel.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).