From: Dan Williams <dcbw@redhat.com>
To: Christoph Hellwig <hch@infradead.org>
Cc: Jeff Garzik <jeff@garzik.org>,
"John W. Linville" <linville@tuxdriver.com>,
linux-wireless@vger.kernel.org, marcelo@kvack.org,
linux-kernel@vger.kernel.org, akpm@osdl.org
Subject: Re: Please pull 'libertas' branch of wireless-2.6
Date: Mon, 07 May 2007 08:03:43 -0400 [thread overview]
Message-ID: <1178539423.3032.24.camel@localhost.localdomain> (raw)
In-Reply-To: <20070507104117.GA31601@infradead.org>
On Mon, 2007-05-07 at 11:41 +0100, Christoph Hellwig wrote:
> On Sat, Mar 03, 2007 at 05:21:40AM +0000, Christoph Hellwig wrote:
> > Umm, I can't remember the updated driver ever beeig posted for review.
> > And to be honest I'd be surprised if it's in a good shape already.
>
> Of course it's not anywhere near good shape. Almost all items from my
> review were completely ignored, and we have another totoally substandard
> wireless driver with crappy thread handling, a huge number of broken private
> ioctls and partially absymal codingstyle.
- things like 11d.[ch] don't have business of being in a driver,
this should be somewhere in common code.
There is no common code for this. mac80211 will eventually grow a
utility library that libertas will hopefully be able to attach to.
- please get rid of the ENTER/LEAVE macros
People have said that many drivers do this, and it's quite useful for
debugging.
- please get rid of all your private ioctls and iwpriv stuff
(should I add !!!! here)
Any ioctls that have equivalents in WEXT or ethtool can certainly be
removed. Mesh ones like fwt_reset, bt_reset, mesh_get_ttl, etc have no
current equivalents and will need to stick around. I've already removed
all the ones that were relevant for WPA and moved them to standard WEXT
calls.
- most of types.h should not be there but you should be using
the types from include/linux/*80211*
I've already updated libertas-2.6 git with a ton of updates for this.
In any case, lets push off any merge until 2.6.23 so the rest of the
comments can be dealt with:
- the __le* annotation issue you mentioned in the mail is important.
- there shouldn't be a LICENSE file in individual driver directories,
especially if it's just plain old GPLv2.
- please get rid of setting -DFOO flags in the Makefile, just use
these directly as config symbols.
- there shouldn't be a README file in the driver directory, this
should be in Documentation/
- please don't use wlan_* foo types. a) this should be structs, not
typedefs, and b) wlan is an utterly generic name for beeing inside
a driver.
- there seems to be lots of tabs vs spaces messups
- there's an awful lot of headers without clear divided
responsibilities,
there should be only a few ones left (internal interfaces and hw
interface basically)
- having lowercase names for lots of hw commands is a very bad idea
for readability
- etc
Dan
> And I didn't even get a reply to my mail addressing the concerns above.
> -
> To unsubscribe from this list: send the line "unsubscribe linux-wireless" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2007-05-07 12:00 UTC|newest]
Thread overview: 44+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20070227205649.GH5826@tuxdriver.com>
2007-02-28 1:01 ` Please pull 'libertas' branch of wireless-2.6 John W. Linville
2007-03-03 1:29 ` Jeff Garzik
2007-03-03 5:21 ` Christoph Hellwig
2007-03-04 15:36 ` Marcelo Tosatti
2007-03-05 14:08 ` Christoph Hellwig
2007-03-07 18:16 ` Marcelo Tosatti
2007-03-07 22:24 ` Christoph Hellwig
2007-03-08 2:40 ` Dan Williams
2007-03-08 8:31 ` Christoph Hellwig
2007-03-08 14:06 ` Michael Buesch
2007-05-07 10:41 ` Christoph Hellwig
2007-05-07 12:03 ` Dan Williams [this message]
2007-05-07 14:11 ` Please pull 'revert-libertas' branch of wireless-2.6 (was Re: Please pull 'libertas' branch of wireless-2.6) John W. Linville
2007-05-07 15:22 ` Jeff Garzik
2007-05-07 15:38 ` John W. Linville
2007-05-07 15:47 ` Dan Williams
2007-05-07 15:48 ` Jeff Garzik
2007-05-07 16:44 ` John W. Linville
2007-05-08 6:12 ` Matt Mackall
2007-05-08 8:28 ` Nick Piggin
2007-05-08 20:59 ` Jeff Garzik
2007-05-08 23:31 ` Nick Piggin
2007-05-08 9:47 ` Pekka Enberg
2007-05-08 20:27 ` Please pull 'revert-libertas' branch of wireless-2.6 David Miller
2007-05-08 20:55 ` Jeff Garzik
2007-05-08 21:29 ` Dan Williams
2007-05-08 22:40 ` Jeff Garzik
2007-05-08 23:41 ` Marcelo Tosatti
2007-05-09 1:27 ` Dan Williams
2007-05-09 21:25 ` Randy Dunlap
2007-05-09 21:41 ` Dan Williams
2007-05-09 21:41 ` Jeff Garzik
2007-05-10 18:35 ` Dan Williams
2007-05-09 21:46 ` Randy Dunlap
2007-05-10 16:56 ` Dan Williams
2007-05-10 20:48 ` Dan Williams
2007-03-16 21:38 Please pull 'libertas' " John W. Linville
-- strict thread matches above, loose matches on Subject: below --
2007-05-11 19:26 John W. Linville
2007-05-11 20:59 ` Jeff Garzik
[not found] <20070529183347.GD3496@tuxdriver.com>
2007-05-30 14:07 ` Jeff Garzik
2007-05-30 15:28 ` Dan Williams
2007-05-31 21:13 ` Dan Williams
2007-05-31 21:16 ` John W. Linville
2007-06-01 21:48 ` Dan Williams
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=1178539423.3032.24.camel@localhost.localdomain \
--to=dcbw@redhat.com \
--cc=akpm@osdl.org \
--cc=hch@infradead.org \
--cc=jeff@garzik.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=marcelo@kvack.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).