From: Jeff Garzik <jgarzik@pobox.com>
To: Linus Torvalds <torvalds@osdl.org>
Cc: Andrew Morton <akpm@osdl.org>,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [git patches] 2.6.x net driver updates
Date: Thu, 12 Jan 2006 17:42:27 -0500 [thread overview]
Message-ID: <20060112224227.GA26888@havoc.gtf.org> (raw)
In-Reply-To: <Pine.LNX.4.64.0601121423120.3535@g5.osdl.org>
On Thu, Jan 12, 2006 at 02:30:19PM -0800, Linus Torvalds wrote:
>
>
> On Thu, 12 Jan 2006, Jeff Garzik wrote:
> >
> > dann frazier:
> > CONFIG_AIRO needs CONFIG_CRYPTO
>
> I think this is done wrong.
>
> It should "select CRYPTO" rather than "depends on CRYPTO".
OK
> Otherwise people won't see it just because they don't have crypto enabled,
> which is not very user-friendly.
>
> Btw, why are these casts there? Either the functions are of the right
> type, or they aren't. In neither case is the cast correct.
>
> I do realize that there are comments in <net/iw_handler.h> that says that
> you should do the cast, but that's no excuse for crap or stupid code.
>
> If it's an issue of trying to make greppable code, why not have
> just the comment?
>
> > @@ -2378,6 +2566,15 @@ static const iw_handler atmel_handler[]
> > (iw_handler) atmel_get_encode, /* SIOCGIWENCODE */
> > (iw_handler) atmel_set_power, /* SIOCSIWPOWER */
> > (iw_handler) atmel_get_power, /* SIOCGIWPOWER */
> > + (iw_handler) NULL, /* -- hole -- */
> > + (iw_handler) NULL, /* -- hole -- */
> ...
>
> Hmm?
Welcome to the awful wireless driver API. This type crapola is a key
thing that needs changing, but its not the only thing. There are also
some nasty wireless APIs which do casts based on variable (passed-in)
struct offsets...
This needs to change to a type-safe thingy like struct ethtool_ops, but
the above is what we were lumped with.
Jeff
next prev parent reply other threads:[~2006-01-12 22:42 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-12 22:13 [git patches] 2.6.x net driver updates Jeff Garzik
2006-01-12 22:30 ` Linus Torvalds
2006-01-12 22:39 ` Andrew Morton
2006-01-12 22:46 ` Linus Torvalds
2006-01-13 17:56 ` Roman Zippel
2006-01-13 19:23 ` Jens Axboe
2006-01-13 19:28 ` Sam Ravnborg
2006-01-13 19:36 ` Jens Axboe
2006-01-14 2:29 ` Adrian Bunk
2006-01-14 5:05 ` Randy.Dunlap
2006-01-12 22:42 ` Jeff Garzik [this message]
2006-01-12 23:14 ` Adrian Bunk
-- strict thread matches above, loose matches on Subject: below --
2006-01-09 17:10 Jeff Garzik
2006-01-03 16:41 Jeff Garzik
2005-11-09 6:53 Jeff Garzik
2005-11-05 19:58 Jeff Garzik
2005-10-29 18:21 Jeff Garzik
2005-10-28 0:42 Jeff Garzik
[not found] <42B456E2.8000500@pobox.com>
2005-06-18 17:51 ` Linus Torvalds
2005-06-18 18:06 ` Linus Torvalds
2005-06-18 18:24 ` Linus Torvalds
2005-06-18 18:36 ` Jeff Garzik
2005-06-18 18:48 ` Linus Torvalds
2005-06-18 20:04 ` Jeff Garzik
2005-06-18 20:23 ` Linus Torvalds
[not found] <4292BA66.8070806@pobox.com>
2005-05-24 6:08 ` Linus Torvalds
2005-05-24 6:25 ` Jeff Garzik
2005-05-24 6:48 ` Linus Torvalds
2005-05-24 7:29 ` Jeff Garzik
2005-05-24 7:46 ` Linus Torvalds
2005-05-24 7:55 ` David Lang
2005-05-24 6:34 ` Jeff Garzik
2005-05-24 6:50 ` Linus Torvalds
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=20060112224227.GA26888@havoc.gtf.org \
--to=jgarzik@pobox.com \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=torvalds@osdl.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).