From: Johannes Berg <johannes@sipsolutions.net>
To: "John W. Linville" <linville@tuxdriver.com>
Cc: linux-wireless <linux-wireless@vger.kernel.org>
Subject: Re: [PATCH] wireless-dev wext updates
Date: Fri, 27 Apr 2007 12:14:25 +0200 [thread overview]
Message-ID: <1177668865.7828.42.camel@johannes.berg> (raw)
In-Reply-To: <20070427014607.GD25332@tuxdriver.com>
[-- Attachment #1: Type: text/plain, Size: 459 bytes --]
On Thu, 2007-04-26 at 21:46 -0400, John W. Linville wrote:
> 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?
Ah, sorry about that, I accidentally diffed against wext with my rtnl
optional patch.
I'll mail you a copy, but for everybody else it's here:
http://johannes.sipsolutions.net/patches/kernel/all/2007-04-27-10:13/037-wext-net-2.6.22.patch
johannes
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 190 bytes --]
prev parent reply other threads:[~2007-04-27 10:14 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 ` [PATCH] wireless-dev wext updates John W. Linville
2007-04-27 9:37 ` Johannes Berg
2007-04-27 10:14 ` 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=1177668865.7828.42.camel@johannes.berg \
--to=johannes@sipsolutions.net \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.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 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.