From: Marcel Holtmann <marcel@holtmann.org>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: netdev <netdev@vger.kernel.org>, Jean Tourrilhes <jt@hpl.hp.com>,
linux-wireless <linux-wireless@vger.kernel.org>,
Linux Kernel list <linux-kernel@vger.kernel.org>
Subject: Re: [RFC] make wext wireless bits optional and deprecate them
Date: Tue, 20 May 2008 19:28:41 +0200 [thread overview]
Message-ID: <57793EAF-9BDF-43DE-8E59-4ADE7AFDC64D@holtmann.org> (raw)
In-Reply-To: <1211303731.6252.105.camel@johannes.berg>
Hi Johannes,
>>> The /sys/class/net/*/wireless/ direcory is, as far as I know, not
>>> used by anyone. Additionally, the same data is available via wext
>>> ioctls. Hence the sysfs files are pretty much useless. This patch
>>> makes them optional and schedules them for removal.
>>
>> it is used by HAL to classify WiFi network cards as net.80211 instead
>> of net.80203 and so we do have an actual user. However HAL only tests
>> for the existence of the directory wireless/.
>>
>> Please fix HAL first before submitting such a patch.
>
> I have filed a patch to fix HAL to use the canonical SIOCGIWNAME at
> https://bugs.freedesktop.org/show_bug.cgi?id=16037. Any further
> objections to this patch?
patch looks good to me.
Regards
Marcel
next prev parent reply other threads:[~2008-05-20 17:29 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-17 12:12 [RFC] make wext wireless bits optional and deprecate them Johannes Berg
2008-05-17 12:16 ` Johannes Berg
2008-05-17 13:45 ` Marcel Holtmann
2008-05-17 13:54 ` Johannes Berg
2008-05-17 14:36 ` Marcel Holtmann
2008-05-17 14:42 ` Johannes Berg
2008-05-18 13:36 ` Dan Williams
2008-05-19 12:16 ` Johannes Berg
2008-05-19 15:24 ` Dan Williams
2008-05-19 15:39 ` Johannes Berg
2008-05-19 15:53 ` Dan Williams
2008-05-19 17:03 ` Jean Tourrilhes
2008-05-19 17:01 ` Jean Tourrilhes
2008-05-20 17:15 ` Johannes Berg
2008-05-20 17:28 ` Marcel Holtmann [this message]
2008-05-21 21:03 ` John W. Linville
2008-05-21 21:37 ` Johannes Berg
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=57793EAF-9BDF-43DE-8E59-4ADE7AFDC64D@holtmann.org \
--to=marcel@holtmann.org \
--cc=johannes@sipsolutions.net \
--cc=jt@hpl.hp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=netdev@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