linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Kalle Valo <kalle.valo@iki.fi>
To: "John W. Linville" <linville@tuxdriver.com>
Cc: Dan Williams <dcbw@redhat.com>,
	"Luis R. Rodriguez" <mcgrof@gmail.com>,
	Dave <kilroyd@googlemail.com>,
	Karl Relton <karllinuxtest.relton@ntlworld.com>,
	dwmw2@infradead.org, linux-wireless@vger.kernel.org
Subject: Re: Insist on cfg80211 for new drivers?
Date: Wed, 01 Jul 2009 23:40:37 +0300	[thread overview]
Message-ID: <87ljn8t9ve.fsf@litku.valot.fi> (raw)
In-Reply-To: <20090701193657.GD3473@tuxdriver.com> (John W. Linville's message of "Wed\, 1 Jul 2009 15\:36\:57 -0400")

"John W. Linville" <linville@tuxdriver.com> writes:

> On Wed, Jul 01, 2009 at 02:35:00PM -0400, Dan Williams wrote:
>
>> That's really all I
>> care about, I don't want another WEXT-based driver accepted; I want all
>> the new ones using cfg80211.
>
> Now there is a discussion we should have had in Berlin...

Yes, we missed this one.

> is it time to insist on cfg80211-based configuration for all new
> drivers?

I vote for yes. In my books wext is depreceated and its use should be
avoided. After Johannes' excellent work we need to start pushing the use
of cfg80211 and nl80211.

-- 
Kalle Valo

  parent reply	other threads:[~2009-07-01 20:40 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-30 19:05 [PATCH] Add prism 2/3 usb adaptor firmware for use with staging/wlan-ng driver Karl Relton
2009-06-30 19:17 ` Luis R. Rodriguez
2009-06-30 21:09   ` Karl Relton
2009-06-30 21:58     ` Luis R. Rodriguez
2009-07-01 16:16       ` Karl Relton
2009-07-01 17:14         ` Luis R. Rodriguez
2009-07-01 17:22           ` Pavel Roskin
2009-07-01 17:51         ` Dave
2009-07-01 18:12           ` Luis R. Rodriguez
2009-07-01 18:35             ` Dan Williams
2009-07-01 19:36               ` Insist on cfg80211 for new drivers? John W. Linville
2009-07-01 19:49                 ` Luis R. Rodriguez
2009-07-01 19:53                 ` Johannes Berg
2009-07-01 20:40                 ` Kalle Valo [this message]
2009-07-01 21:52                 ` Marcel Holtmann
2009-07-01 21:56                   ` Luis R. Rodriguez
2009-07-01 22:08                     ` Marcel Holtmann
2009-07-01 22:13                       ` Greg KH
2009-07-01 22:18                         ` Marcel Holtmann
2009-07-01 22:42                           ` Greg KH
2009-07-02 11:07                           ` Bartlomiej Zolnierkiewicz
2009-07-02 12:44                             ` Dan Williams
2009-07-02  9:19                       ` Christoph Hellwig
2009-07-06 12:52                 ` Johannes Berg
2009-07-06 14:23                   ` John W. Linville
2009-07-06 14:45                   ` Larry Finger
2009-07-06 14:57                     ` Johannes Berg
2009-07-06 15:05                       ` Nick Kossifidis
2009-07-01 19:46         ` [PATCH] Add prism 2/3 usb adaptor firmware for use with staging/wlan-ng driver David Woodhouse
2009-07-02 16:59           ` Karl Relton
2009-06-30 19:39 ` John W. Linville

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=87ljn8t9ve.fsf@litku.valot.fi \
    --to=kalle.valo@iki.fi \
    --cc=dcbw@redhat.com \
    --cc=dwmw2@infradead.org \
    --cc=karllinuxtest.relton@ntlworld.com \
    --cc=kilroyd@googlemail.com \
    --cc=linux-wireless@vger.kernel.org \
    --cc=linville@tuxdriver.com \
    --cc=mcgrof@gmail.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).