From: "John W. Linville" <linville@tuxdriver.com>
To: Bjorge Dijkstra <bjd@jooz.net>
Cc: linux-wireless <linux-wireless@vger.kernel.org>
Subject: Re: status wireless extensions API for new drivers
Date: Thu, 13 Dec 2007 16:31:18 -0500 [thread overview]
Message-ID: <20071213213118.GE3083@tuxdriver.com> (raw)
In-Reply-To: <4761A108.2080005@jooz.net>
On Thu, Dec 13, 2007 at 10:15:52PM +0100, Bjorge Dijkstra wrote:
> We have used the Wireless Extensions API, but I get the impression that
> things are moving towards the cfg/nl80211 API's. Is it still acceptable
> for new drivers trying to get into mainline to use WEXT, or should we
> switch to the new API's?
WEXT is fine for new drivers. At this time cfg80211 does not offer
a suitable replacement.
John
--
John W. Linville
linville@tuxdriver.com
next prev parent reply other threads:[~2007-12-13 21:58 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-13 21:15 status wireless extensions API for new drivers Bjorge Dijkstra
2007-12-13 21:31 ` John W. Linville [this message]
2007-12-13 22:07 ` Bjorge Dijkstra
2007-12-13 22:13 ` John W. Linville
2007-12-13 23:01 ` Bjorge Dijkstra
2007-12-13 21:33 ` Dan Williams
2007-12-13 22:05 ` Bjorge Dijkstra
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=20071213213118.GE3083@tuxdriver.com \
--to=linville@tuxdriver.com \
--cc=bjd@jooz.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).