From: Larry Finger <Larry.Finger@lwfinger.net>
To: Valdis.Kletnieks@vt.edu
Cc: "Gábor Stefanik" <netrolller.3d@gmail.com>,
"Pavel Ivanov" <paivanof@gmail.com>,
"Luis R. Rodriguez" <lrodriguez@atheros.com>,
"Jouni Malinen" <jmalinen@atheros.com>,
"Vasanthakumar Thiagarajan" <vasanth@atheros.com>,
"Senthil Balasubramanian" <senthilkumar@atheros.com>,
linux-wireless@vger.kernel.org, ath9k-devel@venema.h4ckr.net,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] ath9k: make driver usable standalone
Date: Wed, 17 Aug 2011 18:20:34 -0500 [thread overview]
Message-ID: <4E4C4CC2.2070702@lwfinger.net> (raw)
In-Reply-To: <24649.1313621503@turing-police.cc.vt.edu>
On 08/17/2011 05:51 PM, Valdis.Kletnieks@vt.edu wrote:
> On Wed, 17 Aug 2011 18:25:49 +0200, Gábor Stefanik said:
>
>> Iwconfig and iwlist are themselves deprecated. Iw is the new wireless
>> configuration tool.
>
> Somebody better tell Fedora Rawhide - as of the version released on July 27,
> their 'initscripts' RPM was still using iwconfig in /etc/sysconfig/network-scripts/ifup-wireless
>
> So don't be quite so fast to be declaring WIRELESS_EXT dead just yet.
Well, any distro is free to include any package they want. They can even devote
resources to maintaining it after it is abandoned. Given the feelings among
developers about the WEXT methods, I doubt that will happen.
The distro is also including one of the drivers that need WEXT, which is what
the OP refused to do. If and when all such drivers are converted or removed, the
distro is still free to patch in the WEXT code, but again I doubt that will happen.
Anyone using deprecated methods has been warned.
Larry
next prev parent reply other threads:[~2011-08-17 23:20 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-17 3:28 [PATCH] ath9k: make driver usable standalone Pavel Ivanov
2011-08-17 5:57 ` Gábor Stefanik
2011-08-17 15:56 ` Pavel Ivanov
2011-08-17 16:25 ` Gábor Stefanik
2011-08-17 22:51 ` Valdis.Kletnieks
2011-08-17 23:20 ` Larry Finger [this message]
2011-08-18 19:18 ` Dan Williams
2011-08-18 4:01 ` Pavel Ivanov
2011-08-18 5:19 ` Adrian Chadd
2011-08-18 19:20 ` Dan Williams
2011-08-18 19:30 ` Pavel Ivanov
2011-08-18 20:35 ` Dan Williams
2011-08-18 22:56 ` Pavel Ivanov
2011-08-19 1:25 ` Johannes Berg
2011-08-19 4:27 ` Pavel Ivanov
2011-08-18 21:26 ` Luis R. Rodriguez
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=4E4C4CC2.2070702@lwfinger.net \
--to=larry.finger@lwfinger.net \
--cc=Valdis.Kletnieks@vt.edu \
--cc=ath9k-devel@venema.h4ckr.net \
--cc=jmalinen@atheros.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=lrodriguez@atheros.com \
--cc=netrolller.3d@gmail.com \
--cc=paivanof@gmail.com \
--cc=senthilkumar@atheros.com \
--cc=vasanth@atheros.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