From: Jeff Garzik <jgarzik@pobox.com>
To: jt@hpl.hp.com
Cc: Pavel Roskin <proski@gnu.org>, Netdev <netdev@oss.sgi.com>
Subject: Re: linux-wireless mailing list
Date: Wed, 10 Mar 2004 12:46:09 -0500 [thread overview]
Message-ID: <404F5461.80000@pobox.com> (raw)
In-Reply-To: <20040305040352.GA16669@bougret.hpl.hp.com>
Jean Tourrilhes wrote:
> +static inline int rtnetlink_standard_call(struct net_device * dev,
> + struct iw_event * request,
> + int request_len,
> + iw_handler handler)
> +{
> + const struct iw_ioctl_description * descr = NULL;
> + unsigned int cmd;
> + union iwreq_data * wrqu;
> + int hdr_len;
> + struct iw_request_info info;
> + int ret = -EINVAL;
> +
> + /* Get the description of the IOCTL */
> + cmd = request->cmd;
> + if((cmd - SIOCIWFIRST) >= standard_ioctl_num)
> + return -EOPNOTSUPP;
> + descr = &(standard_ioctl[cmd - SIOCIWFIRST]);
OK, this patch looks good to me.
There is one piece we need to change though, that will cause the size of
this patch to increase a bit.
Look at ethtool_ops, and net/core/ethtool.c, in the current upstream 2.4
and 2.6 trees.
A key goal of mine is to completely eliminate the union and the
iw_handler type. To increase type-safety, and to decrease the pain of
going through 32<->64-bit translation layers, each wireless hook needs
to have a specific (not generic) interface (a la ethtool_ops).
Jeff
next prev parent reply other threads:[~2004-03-10 17:46 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <Pine.LNX.4.58.0403031656090.22365@marabou.research.att.com>
2004-03-04 3:08 ` linux-wireless mailing list Jeff Garzik
2004-03-04 17:34 ` Jean Tourrilhes
2004-03-05 4:03 ` Jean Tourrilhes
2004-03-10 17:46 ` Jeff Garzik [this message]
2004-03-10 18:06 ` Jean Tourrilhes
2004-03-10 18:25 ` Jeff Garzik
2004-03-10 23:53 ` Jean Tourrilhes
2004-03-12 0:12 ` Jean Tourrilhes
[not found] ` <20040303233343.GA14803@bougret.hpl.hp.com>
2004-03-04 7:08 ` Pavel Roskin
2004-03-05 4:08 ` Jouni Malinen
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=404F5461.80000@pobox.com \
--to=jgarzik@pobox.com \
--cc=jt@hpl.hp.com \
--cc=netdev@oss.sgi.com \
--cc=proski@gnu.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.