From: Willy Tarreau <willy@w.ods.org>
To: Jeff Garzik <jgarzik@pobox.com>
Cc: Rusty Russell <rusty@rustcorp.com.au>, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] PARAM 2/4
Date: Sat, 16 Nov 2002 08:15:09 +0100 [thread overview]
Message-ID: <20021116071509.GC553@alpha.home.local> (raw)
In-Reply-To: <3DD57A84.2070805@pobox.com>
On Fri, Nov 15, 2002 at 05:51:48PM -0500, Jeff Garzik wrote:
[snip]
> 2) "proper", converted-to-Rusty-style driver code is going to have
>
> MODULE_blah
> MODULE_foo
> MODULE_bar
> PARAM
>
> You think that looks good??
>
> 3) modules a.k.a. drivers are going to be the more common users of this
> interface.
[snip]
> PARAM is ugly in drivers, and way too generic.
Why not DRIVER_PARAM in this case ? It's enough explicit and not misleading.
I too agree that PARAM is a bit too generic.
Cheers,
Willy
next prev parent reply other threads:[~2002-11-16 7:08 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-11-15 22:26 [PATCH] PARAM 2/4 Rusty Russell
2002-11-15 22:51 ` Jeff Garzik
2002-11-15 23:17 ` Rusty Russell
2002-11-16 7:15 ` Willy Tarreau [this message]
2002-11-17 18:00 ` Linus Torvalds
2002-11-17 18:21 ` Rusty Russell
2002-11-17 18:29 ` 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=20021116071509.GC553@alpha.home.local \
--to=willy@w.ods.org \
--cc=jgarzik@pobox.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rusty@rustcorp.com.au \
/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