From: Johannes Berg <johannes@sipsolutions.net>
To: Jiri Benc <jbenc@suse.cz>
Cc: netdev <netdev@vger.kernel.org>, Jeff Garzik <jgarzik@pobox.com>,
"John W. Linville" <linville@tuxdriver.com>,
Simon Barber <simon@devicescape.com>,
Michael Buesch <mbuesch@freenet.de>,
Ivo van Doorn <ivdoorn@gmail.com>,
Michael Wu <flamingice@sourmilk.net>,
Jouni Malinen <jkm@devicescape.com>,
Daniel Drake <dsd@gentoo.org>, Hong Liu <hong.liu@intel.com>,
"Luis R. Rodriguez" <mcgrof@gmail.com>,
James Ketrenos <jketreno@linux.intel.com>,
David Kimdon <david.kimdon@devicescape.com>,
Udayan Singh <udayan.singh@gmail.com>
Subject: Re: wireless notes / pre d80211 merge
Date: Wed, 15 Nov 2006 11:16:44 +0100 [thread overview]
Message-ID: <1163585804.2705.44.camel@ux156> (raw)
In-Reply-To: <20061115110549.2fa3866c@griffin.suse.cz>
On Wed, 2006-11-15 at 11:05 +0100, Jiri Benc wrote:
> I wasn't in times when there was no cfg80211. But now... yes, you're
> right. The sysfs ieee80211 class exports just some interesting
> informations (we already agreed that add_interface and remove_interface
> would go away). Feel free to move it wherever you think is appropriate.
Even with cfg80211 we have the wiphy concept embedded in there. Not much
difference because we still have to do tc on wmasterN and "wiconf" on
wiphyN. So that doesn't really change anything. Now, we could of course
drop the wiphy concept from cfg80211 easily and require doing all these
things on wmasterN. That's the option I considered in section (8). I
don't like it too much, but I think I could live with it.
johannes
prev parent reply other threads:[~2006-11-15 10:15 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-14 22:19 wireless notes / pre d80211 merge Johannes Berg
2006-11-15 0:11 ` Jiri Benc
2006-11-15 2:10 ` Simon Barber
2006-11-15 9:43 ` Jiri Benc
2006-11-15 10:13 ` Johannes Berg
2006-11-15 18:47 ` Jeff Garzik
2006-11-15 10:03 ` Johannes Berg
2006-11-15 18:46 ` Jeff Garzik
2006-11-15 9:16 ` Johannes Berg
2006-11-15 10:05 ` Jiri Benc
2006-11-15 10:16 ` 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=1163585804.2705.44.camel@ux156 \
--to=johannes@sipsolutions.net \
--cc=david.kimdon@devicescape.com \
--cc=dsd@gentoo.org \
--cc=flamingice@sourmilk.net \
--cc=hong.liu@intel.com \
--cc=ivdoorn@gmail.com \
--cc=jbenc@suse.cz \
--cc=jgarzik@pobox.com \
--cc=jketreno@linux.intel.com \
--cc=jkm@devicescape.com \
--cc=linville@tuxdriver.com \
--cc=mbuesch@freenet.de \
--cc=mcgrof@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=simon@devicescape.com \
--cc=udayan.singh@gmail.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;
as well as URLs for NNTP newsgroup(s).