From: Joe Perches <joe@perches.com>
To: linux-kernel@vger.kernel.org
Cc: orinoco-users@lists.sourceforge.net, Zhu Yi <yi.zhu@intel.com>,
Reinette Chatre <reinette.chatre@intel.com>,
David Gibson <hermes@gibson.dropbear.id.au>,
netdev@vger.kernel.org, orinoco-devel@lists.sourceforge.net,
linux-wireless@vger.kernel.org, cbe-oss-dev@ozlabs.org,
Intel Linux Wireless <ilw@linux.intel.com>,
linuxppc-dev@ozlabs.org,
Arnaldo Carvalho de Melo <acme@ghostprotocols.net>,
Johannes Berg <johannes@sipsolutions.net>,
Richard Kennedy <richard@rsk.demon.co.uk>,
"David S. Miller" <davem@davemloft.net>,
Pavel Roskin <proski@gnu.org>
Subject: [PATCH v3 0/9] wireless: Use macros from wireless.h
Date: Thu, 18 Mar 2010 18:29:31 -0700 [thread overview]
Message-ID: <cover.1268961559.git.joe@perches.com> (raw)
Create a IW_HANDLER macro for iw_handler array entries in wireless.h
Use the wireless.h macros in various wireless files
Use starting index define SIOCIWFIRST where appropriate
Remove local #defines of IW_IOCTL
Remove STD_IW_HANDLER macro in orinoco, use IW_HANDLER instead
Joe Perches (9):
include/linux/wireless.h: Add IW_HANDLER macro to initialize array entry
wireless.h: Use SIOCIWFIRST not SIOCSIWCOMMIT for range check
include/net/iw_handler.h: Use SIOCIWFIRST not SIOCSIWCOMMIT in comment
net/wireless/wext_core.c: Use IW_IOCTL_IDX macro
net/wireless/wext-core.c: Use IW_EVENT_IDX macro
drivers/net/wireless: Use IW_HANDLER macro
drivers/net: Remove local #define IW_IOCTL, use IW_HANDLER
orinoco/wext.c: Remove local #define STD_IW_HANDLER
drivers/net/wireless/ray_cs.c: Use iw_handler function prototypes
drivers/net/ps3_gelic_wireless.c | 35 +++---
drivers/net/wireless/ipw2x00/ipw2200.c | 83 ++++++-------
drivers/net/wireless/orinoco/wext.c | 94 +++++++-------
drivers/net/wireless/ray_cs.c | 212 +++++++++++++++-----------------
drivers/net/wireless/wl3501_cs.c | 52 ++++----
include/linux/wireless.h | 4 +-
include/net/iw_handler.h | 2 +-
net/wireless/wext-core.c | 134 ++++++++++----------
8 files changed, 298 insertions(+), 318 deletions(-)
next reply other threads:[~2010-03-19 1:29 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-19 1:29 Joe Perches [this message]
2010-03-19 1:29 ` [PATCH v3 3/9] include/net/iw_handler.h: Use SIOCIWFIRST not SIOCSIWCOMMIT in comment Joe Perches
2010-03-19 1:29 ` [PATCH v3 4/9] net/wireless/wext_core.c: Use IW_IOCTL_IDX macro Joe Perches
2010-03-19 1:29 ` [PATCH v3 5/9] net/wireless/wext-core.c: Use IW_EVENT_IDX macro Joe Perches
2010-03-19 1:29 ` [PATCH v3 6/9] drivers/net/wireless: Use IW_HANDLER macro Joe Perches
2010-03-19 1:29 ` [PATCH v3 7/9] drivers/net: Remove local #define IW_IOCTL, use IW_HANDLER Joe Perches
[not found] ` <cover.1268961559.git.joe-6d6DIl74uiNBDgjK7y7TUQ@public.gmane.org>
2010-03-19 1:29 ` [PATCH v3 8/9] orinoco/wext.c: Remove local #define STD_IW_HANDLER Joe Perches
2010-03-19 1:29 ` [PATCH v3 9/9] drivers/net/wireless/ray_cs.c: Use iw_handler function prototypes Joe Perches
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=cover.1268961559.git.joe@perches.com \
--to=joe@perches.com \
--cc=acme@ghostprotocols.net \
--cc=cbe-oss-dev@ozlabs.org \
--cc=davem@davemloft.net \
--cc=hermes@gibson.dropbear.id.au \
--cc=ilw@linux.intel.com \
--cc=johannes@sipsolutions.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=netdev@vger.kernel.org \
--cc=orinoco-devel@lists.sourceforge.net \
--cc=orinoco-users@lists.sourceforge.net \
--cc=proski@gnu.org \
--cc=reinette.chatre@intel.com \
--cc=richard@rsk.demon.co.uk \
--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).