From: Johannes Berg <johannes@sipsolutions.net>
To: Jouni Malinen <jkmaline@cc.hut.fi>
Cc: jt@hpl.hp.com, "John W. Linville" <linville@tuxdriver.com>,
netdev@vger.kernel.org, Javier Achirica <achirica@gmail.com>,
Simon Kelley <simon@thekelleys.org.uk>,
"James P. Ketrenos" <ipw2100-admin@linux.intel.com>,
Zhu Yi <yi.zhu@intel.com>, Pavel Roskin <proski@gnu.org>,
"Luis R. Rodriguez" <mcgrof@ruslug.rutgers.edu>,
Jeroen Vreeken <pe1rxq@amsat.org>,
Michael Wu <flamingice@sourmilk.net>,
Denis Vlasenko <vda@ilport.com.ua>,
Michael Buesch <mbuesch@freenet.de>
Subject: Re: [PATCH 2.6.18] WE-21 support (core API)
Date: Thu, 31 Aug 2006 16:00:05 +0200 [thread overview]
Message-ID: <1157032805.16040.21.camel@ux156> (raw)
In-Reply-To: <20060831135112.GA6097@jm.kir.nu>
On Thu, 2006-08-31 at 06:51 -0700, Jouni Malinen wrote:
> I don't know about the others, but long/short retry limits have users
> (e.g., Host AP driver) and these drivers are currently forced to use a
> hack to do this without this cleanup. Furthermore, this part does not
> add a new ioctl.
It does, however, add new parameters and things that'd need to be
translated in the compat layer later. Hence, even there, I'd prefer to
add them directly into nl80211. However, the compat code for that
shouldn't be that bad, so I can see that as a softer target :) But I
don't want to see new ioctls for sure.
johannes
next prev parent reply other threads:[~2006-08-31 13:59 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-30 0:56 [PATCH 2.6.18] WE-21 support (core API) Jean Tourrilhes
2006-08-31 13:32 ` Johannes Berg
2006-08-31 13:51 ` Jouni Malinen
2006-08-31 14:00 ` Johannes Berg [this message]
2006-09-06 20:55 ` [RFC] Alternate " John W. Linville
2006-09-06 21:09 ` Michael Buesch
2006-09-06 21:30 ` Jean Tourrilhes
2006-09-08 14:29 ` John W. Linville
2006-09-08 16:13 ` Jean Tourrilhes
2006-09-08 20:04 ` John W. Linville
2006-09-11 9:08 ` Johannes Berg
[not found] ` <20060911162608.GA31459@bougret.hpl.hp.com>
[not found] ` <1158050637.2854.16.camel@ux156>
2006-09-12 16:17 ` Jean Tourrilhes
2006-09-13 6:17 ` Johannes Berg
2006-09-06 21:43 ` Larry Finger
2006-09-07 6:42 ` Johannes Berg
2006-08-31 17:12 ` [PATCH 2.6.18] " Jean Tourrilhes
2006-08-31 17:57 ` Michael Buesch
2006-09-01 6:56 ` Johannes Berg
2006-09-01 6:54 ` Johannes Berg
2006-09-01 16:35 ` Jean Tourrilhes
2006-09-01 18:55 ` Michael Buesch
2006-09-01 22:10 ` Jean Tourrilhes
2006-09-02 0:47 ` Michael Buesch
2006-09-04 8:17 ` Johannes Berg
2006-09-04 8:35 ` Johannes Berg
2006-09-04 14:13 ` Stuffed Crust
2006-09-05 17:06 ` Jean Tourrilhes
2006-09-01 22:27 ` Ulrich Kunitz
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=1157032805.16040.21.camel@ux156 \
--to=johannes@sipsolutions.net \
--cc=achirica@gmail.com \
--cc=flamingice@sourmilk.net \
--cc=ipw2100-admin@linux.intel.com \
--cc=jkmaline@cc.hut.fi \
--cc=jt@hpl.hp.com \
--cc=linville@tuxdriver.com \
--cc=mbuesch@freenet.de \
--cc=mcgrof@ruslug.rutgers.edu \
--cc=netdev@vger.kernel.org \
--cc=pe1rxq@amsat.org \
--cc=proski@gnu.org \
--cc=simon@thekelleys.org.uk \
--cc=vda@ilport.com.ua \
--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).