From: Johannes Berg <johannes@sipsolutions.net>
To: netdev <netdev@vger.kernel.org>
Cc: Jiri Benc <jbenc@suse.cz>, "John W. Linville" <linville@tuxdriver.com>
Subject: Re: cfg80211 take 7
Date: Fri, 06 Oct 2006 17:07:49 +0200 [thread overview]
Message-ID: <1160147269.2715.88.camel@ux156> (raw)
In-Reply-To: <1160146790.2715.82.camel@ux156>
Maybe this time it'll take the announcement too?
---
I have
* addressed Dan's comments about naming a few things and
also fixed the problems he pointed out
* moved wext from net/core/wireless.c to net/wireless/wext-old.c
* added compat hunking for WE to cfg80211, finally completely
separating the userspace interface and the internal interface
* made it possible to port drivers to cfg80211 call by call!
* fixed a bug with locking in core.c
I have not
* added get_scan
* added event notification
Have fun. Oh, I can put this into a git tree too if you think that'd be
useful for further collaboration. However, I'm thinking that wireless-dev
could also be used since this doesn't really break anything, it just adds
new code that might not be in use yet, but should be fairly good to use
should anyone want that.
I guess what I'm trying to say with that is that there's no way I can finish
this all by myself, I also need sleep sometimes ;) I thank everyone for
their review and suppose that more people read it than commented (which is
probably a good thing). Hopefully I can motivate you with these patches that
should ease migration to actually help with code as well :)
johannes
next prev parent reply other threads:[~2006-10-06 15:06 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-06 14:59 cfg80211 take 7 Johannes Berg
2006-10-06 15:07 ` Johannes Berg [this message]
2006-10-09 11:22 ` Stefan Rompf
[not found] ` <200610091322.10495.stefan@loplof.de>
2006-10-09 11:49 ` Johannes Berg
2006-10-09 12:52 ` Stefan Rompf
2006-10-09 14:16 ` Larry Finger
2006-10-09 18:38 ` David Kimdon
2006-10-09 22:01 ` 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=1160147269.2715.88.camel@ux156 \
--to=johannes@sipsolutions.net \
--cc=jbenc@suse.cz \
--cc=linville@tuxdriver.com \
--cc=netdev@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).