From: Ivo van Doorn <ivdoorn@gmail.com>
To: "John W. Linville" <linville@tuxdriver.com>
Cc: Johannes Berg <johannes@sipsolutions.net>,
Jiri Benc <jbenc@suse.cz>,
netdev@vger.kernel.org, Michael Wu <flamingice@sourmilk.net>,
Michael Buesch <mb@bu3sch.de>, Hong Liu <hong.liu@intel.com>
Subject: Re: [PATCH 1/6] d80211: change the cookie to be opaque
Date: Sun, 5 Nov 2006 16:20:29 +0100 [thread overview]
Message-ID: <200611051620.29687.IvDoorn@gmail.com> (raw)
In-Reply-To: <20061103041455.GE2989@tuxdriver.com>
On Friday 03 November 2006 05:15, John W. Linville wrote:
> On Fri, Nov 03, 2006 at 01:46:31AM +0100, Johannes Berg wrote:
> >
> > > Ok, that one was wrong. But what is it doing in the public API? We need
> > > to remove it from the public API and leave struct net_device *dev as the
> > > parameter. adm8211 actually uses it and increases the tx_fifo_error
> > > counter, but that's a bit strange.
> >
> > Fixed, and since, as always, netdev doesn't like my patches, they're
> > here instead:
> >
> > http://johannes.sipsolutions.net/files/d80211-mdev-cleanup/
> >
> > I also added d80211-reduce-mdev.patch which reduces stupid mdev usage,
> > but see the description in the patch itself.
>
> 403 Forbidden (shouldn't that be Verboten? :-)
>
> FWIW, I have the other 6 patches on the 'pending' branch of
> wireless-dev. Driver authors, please proceed accordingly.
I am currently working on the fixes for rt2x00, the above patches look very good,
and also provide me with a chance to cleanup some garbage in rt2x00. :)
I'll make the patches for this part of my patch series which I will send to the netdev
list in 1 or 2 weeks. (I cannot do it any sooner due to school and work).
Ivo
next prev parent reply other threads:[~2006-11-05 15:20 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20061102223854.692274000@sipsolutions.net>
2006-11-02 23:28 ` [PATCH 0/6] rework d80211 cookie pointer Michael Wu
[not found] ` <20061102230013.960383000@sipsolutions.net>
2006-11-03 0:22 ` [PATCH 1/6] d80211: change the cookie to be opaque Johannes Berg
2006-11-03 0:46 ` Johannes Berg
2006-11-03 4:15 ` John W. Linville
2006-11-03 8:41 ` Johannes Berg
2006-11-05 15:20 ` Ivo van Doorn [this message]
2006-11-05 15:24 ` Johannes Berg
2006-11-03 9:21 ` Johannes Berg
2006-11-03 2:28 ` Michael Wu
2006-11-03 8:42 ` Johannes Berg
2006-11-03 19:04 ` [PATCH 0/6] rework d80211 cookie pointer Michael Wu
2006-11-03 19:08 ` Johannes Berg
2006-11-03 22:14 ` Michael Wu
2006-11-03 23:10 ` Johannes Berg
[not found] ` <20061102230015.186648000@sipsolutions.net>
2006-11-03 21:49 ` [PATCH 3/6] d80211: add a perm_addr hardware property Michael Wu
2006-11-03 23:19 ` Johannes Berg
[not found] ` <20061102230015.555750000@sipsolutions.net>
2006-11-03 22:27 ` [PATCH 4/6] d80211: add a struct device* " Michael Wu
2006-11-03 23:21 ` Johannes Berg
2006-11-03 23:46 ` Johannes Berg
[not found] ` <20061102230016.080591000@sipsolutions.net>
2006-11-03 22:43 ` [PATCH 5/6] d80211: add a ethtool_ops " Michael Wu
2006-11-03 23:22 ` 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=200611051620.29687.IvDoorn@gmail.com \
--to=ivdoorn@gmail.com \
--cc=flamingice@sourmilk.net \
--cc=hong.liu@intel.com \
--cc=jbenc@suse.cz \
--cc=johannes@sipsolutions.net \
--cc=linville@tuxdriver.com \
--cc=mb@bu3sch.de \
--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).