From: Jeff Garzik <jeff@garzik.org>
To: Jiri Benc <jbenc@suse.cz>
Cc: Johannes Berg <johannes@sipsolutions.net>,
netdev <netdev@vger.kernel.org>,
"John W. Linville" <linville@tuxdriver.com>,
Jouni Malinen <jkm@devicescape.com>,
Simon Barber <simon@devicescape.com>,
Hong Liu <hong.liu@intel.com>, Ivo van Doorn <ivdoorn@gmail.com>,
Michael Wu <flamingice@sourmilk.net>,
Michael Buesch <mbuesch@freenet.de>,
David Kimdon <david.kimdon@devicescape.com>,
James Ketrenos <jketreno@linux.intel.com>
Subject: Re: [PATCH 0/11] convert d80211 to a proper protocol
Date: Wed, 08 Nov 2006 08:36:04 -0500 [thread overview]
Message-ID: <4551DD44.7000004@garzik.org> (raw)
In-Reply-To: <20061108125844.46831cda@griffin.suse.cz>
Jiri Benc wrote:
> On Mon, 06 Nov 2006 22:09:54 +0100, Johannes Berg wrote:
>>> What did happen with
>>> d80211: add a function to get the wiphy index
>>> d80211: add a perm_addr hardware property
>>> d80211: add a struct device* hardware property
>>> d80211: add a ethtool_ops hardware property
>>> patches?
>> Well after some chat with a few people I decided that it was stupid and
>> not very maintainable to copy all the fields in net_device to a new
>> structure.
>
> Ok. Personally, I don't care if we pass net_device or ieee80211_local
> to drivers. I see pros and cons of both solutions.
Agreed. Though if using ieee80211_local, please remove the "_local". A
better name is needed.
Jeff
next prev parent reply other threads:[~2006-11-08 13:36 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-05 15:39 [PATCH 0/11] convert d80211 to a proper protocol Johannes Berg
2006-11-05 16:54 ` Ivo van Doorn
2006-11-05 17:05 ` Johannes Berg
2006-11-05 17:09 ` Johannes Berg
2006-11-05 17:06 ` Johannes Berg
2006-11-06 20:01 ` Jiri Benc
2006-11-06 21:09 ` Johannes Berg
2006-11-08 11:58 ` Jiri Benc
2006-11-08 12:33 ` Johannes Berg
2006-11-08 13:36 ` Jeff Garzik [this message]
2006-11-06 23:06 ` Johannes Berg
2006-11-08 12:09 ` Jiri Benc
2006-11-08 12:53 ` Johannes Berg
2006-11-07 18:52 ` Johannes Berg
2006-11-07 19:02 ` Ivo van Doorn
2006-11-07 20:33 ` 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=4551DD44.7000004@garzik.org \
--to=jeff@garzik.org \
--cc=david.kimdon@devicescape.com \
--cc=flamingice@sourmilk.net \
--cc=hong.liu@intel.com \
--cc=ivdoorn@gmail.com \
--cc=jbenc@suse.cz \
--cc=jketreno@linux.intel.com \
--cc=jkm@devicescape.com \
--cc=johannes@sipsolutions.net \
--cc=linville@tuxdriver.com \
--cc=mbuesch@freenet.de \
--cc=netdev@vger.kernel.org \
--cc=simon@devicescape.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).