From: Johannes Berg <johannes@sipsolutions•net>
To: netdev@vger•kernel.org
Cc: linux-wireless@vger•kernel.org
Subject: [PATCH 0/3] wireless extensions improvements
Date: Wed, 24 Jun 2009 13:34:47 +0200 [thread overview]
Message-ID: <20090624113447.441667549@sipsolutions.net> (raw)
Hi,
This series contains three improvements to wireless
extensions:
1) make them network namespace aware, as discussed
previously
2) optimise the event sending code and fix a small
heap information leak
3) do some generic work and make it possible to send
compat netlink events, and make wext do this
Because the third patch depends on the first two (it
could be made not to, if you wish) but touches generic
networking stuff, I'd like to have all of these included
in net-next instead of John's wireless tree, all the
other wireless work can be done independently of these.
johannes
next reply other threads:[~2009-06-24 11:38 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-24 11:34 Johannes Berg [this message]
2009-06-24 11:34 ` [PATCH 1/3] wireless extensions: make netns aware Johannes Berg
2009-06-24 11:34 ` [PATCH 2/3] wext: optimise, comment and fix event sending Johannes Berg
2009-06-24 11:34 ` [PATCH 3/3] net/compat/wext: send different messages to compat tasks Johannes Berg
2009-07-01 21:26 ` [PATCH 3/3 v3] " Johannes Berg
[not found] ` <1246483562.8154.11.camel-YfaajirXv2244ywRPIzf9A@public.gmane.org>
2009-07-15 16:08 ` David Miller
2009-06-25 23:18 ` [PATCH 0/3] wireless extensions improvements David Miller
[not found] ` <20090625.161817.112930127.davem-fT/PcQaiUtIeIZ0/mPfg9Q@public.gmane.org>
2009-06-26 5:46 ` John W. Linville
2009-06-26 20:12 ` 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=20090624113447.441667549@sipsolutions.net \
--to=johannes@sipsolutions$(echo .)net \
--cc=linux-wireless@vger$(echo .)kernel.org \
--cc=netdev@vger$(echo .)kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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