From: Johannes Berg <johannes@sipsolutions.net>
To: John Linville <linville@tuxdriver.com>
Cc: linux-wireless <linux-wireless@vger.kernel.org>
Subject: wext net-next-2.6 work
Date: Mon, 27 Jul 2009 10:55:14 +0200 [thread overview]
Message-ID: <1248684914.19945.48.camel@johannes.local> (raw)
[-- Attachment #1: Type: text/plain, Size: 1112 bytes --]
John,
I don't know how much trouble it is, but if it's not a problem I would
appreciate if you could cherry-pick a few patches from net-next-2.6 into
wireless-testing -- just in case somebody wants to test with 32-bit
userland on 64-bit.
The relevant patches are
commit b333b3d22822cf9b295990866798e9239c9dee72
Author: Johannes Berg <johannes@sipsolutions.net>
Date: Wed Jun 24 01:34:48 2009 +0000
wireless extensions: make netns aware
commit 4f45b2cd4e78b5e49d7d41548345b879d3fdfeae
Author: Johannes Berg <johannes@sipsolutions.net>
Date: Wed Jun 24 01:34:49 2009 +0000
wext: optimise, comment and fix event sending
commit 1dacc76d0014a034b8aca14237c127d7c19d7726
Author: Johannes Berg <johannes@sipsolutions.net>
Date: Wed Jul 1 11:26:02 2009 +0000
net/compat/wext: send different messages to compat tasks
in this order. I had to send them to net-next-2.6, as you probably
remember, because touching lots of other code in the third patch, but
semantically I think they should be part of wireless-testing since they
mostly affect wireless.
johannes
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 801 bytes --]
reply other threads:[~2009-07-27 8:55 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=1248684914.19945.48.camel@johannes.local \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox