From: Johannes Berg <johannes@sipsolutions.net>
To: Joe Perches <joe@perches.com>
Cc: orinoco-users@lists.sourceforge.net, Zhu Yi <yi.zhu@intel.com>,
Reinette Chatre <reinette.chatre@intel.com>,
Corey Thomas <coreythomas@charter.net>,
David Gibson <hermes@gibson.dropbear.id.au>,
netdev@vger.kernel.org, orinoco-devel@lists.sourceforge.net,
linux-wireless@vger.kernel.org, linux-kernel@vger.kernel.org,
Intel Linux Wireless <ilw@linux.intel.com>,
linuxppc-dev@ozlabs.org,
Arnaldo Carvalho de Melo <acme@ghostprotocols.net>,
cbe-oss-dev@ozlabs.org, Richard Kennedy <richard@rsk.demon.co.uk>,
"David S. Miller" <davem@davemloft.net>,
Pavel Roskin <proski@gnu.org>
Subject: Re: [PATCH v2 0/7] wireless: Use macros from wireless.h
Date: Thu, 18 Mar 2010 09:21:53 -0700 [thread overview]
Message-ID: <1268929313.4005.9.camel@jlt3.sipsolutions.net> (raw)
In-Reply-To: <cover.1268892663.git.joe@perches.com>
On Wed, 2010-03-17 at 23:21 -0700, Joe Perches wrote:
> Move the STD_IW_HANDLER macro from orinoco to wireless.h
> Use the wireless.h macros in various wireless files
> Remove local #defines of IW_IOCTL
I really don't want to debug any breakage here, but otherwise I don't
care and this is fine with me.
johannes
prev parent reply other threads:[~2010-03-18 16:21 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-18 6:21 [PATCH v2 0/7] wireless: Use macros from wireless.h Joe Perches
2010-03-18 6:21 ` [PATCH v2 5/7] drivers/net: Remove local #define IW_IOCTL, use STD_IW_HANDLER Joe Perches
2010-03-31 17:55 ` Geoff Levand
2010-03-18 16:21 ` Johannes Berg [this message]
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=1268929313.4005.9.camel@jlt3.sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=acme@ghostprotocols.net \
--cc=cbe-oss-dev@ozlabs.org \
--cc=coreythomas@charter.net \
--cc=davem@davemloft.net \
--cc=hermes@gibson.dropbear.id.au \
--cc=ilw@linux.intel.com \
--cc=joe@perches.com \
--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).