From: "John W. Linville" <linville@tuxdriver.com>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: linux-wireless <linux-wireless@vger.kernel.org>
Subject: Re: [PATCH] wireless-dev wext updates
Date: Thu, 26 Apr 2007 21:46:07 -0400 [thread overview]
Message-ID: <20070427014607.GD25332@tuxdriver.com> (raw)
In-Reply-To: <1177438546.3528.39.camel@johannes.berg>
On Tue, Apr 24, 2007 at 08:15:46PM +0200, Johannes Berg wrote:
> This patch brings the wext in wireless-dev in line with the wext in
> net-2.6.22 (after the patches I just submitted) and removes the
> cfg80211/wext compat stuff.
>
> As long as cfg80211 holds the rtnl we'll be able to just hook into
> dev->do_ioctl for the compat code instead.
>
> Signed-off-by: Johannes Berg <johannes@sipsolutions.net>
Johannes,
This didn't apply cleanly to the master branch of the current
wireless-dev. Could you be sure to pull an up-to-date copy and rediff?
Thanks!
John
--
John W. Linville
linville@tuxdriver.com
next parent reply other threads:[~2007-04-27 2:22 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1177438546.3528.39.camel@johannes.berg>
2007-04-27 1:46 ` John W. Linville [this message]
2007-04-27 9:37 ` [PATCH] wireless-dev wext updates Johannes Berg
2007-04-27 10:14 ` Johannes Berg
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=20070427014607.GD25332@tuxdriver.com \
--to=linville@tuxdriver.com \
--cc=johannes@sipsolutions.net \
--cc=linux-wireless@vger.kernel.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 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).