From: Rusty Russell <rusty@rustcorp.com.au>
To: Linus Torvalds <torvalds@transmeta.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] PARAM 2/4
Date: Mon, 18 Nov 2002 05:21:16 +1100 [thread overview]
Message-ID: <20021117182227.82F332C059@lists.samba.org> (raw)
In-Reply-To: Your message of "Sun, 17 Nov 2002 10:00:17 -0800." <Pine.LNX.4.44.0211170953140.4425-100000@home.transmeta.com>
In message <Pine.LNX.4.44.0211170953140.4425-100000@home.transmeta.com> you wri
te:
>
> On Sat, 16 Nov 2002, Rusty Russell wrote:
> > MODULE_PARAM is misleading and wrong.
>
> Why is MODULE_PARAM() misleading and wrong? I think it's a lot more
> descriptive, and these things are "modules" whether they are actually
> compiled in or not.
I've already conceded this to Jeff Garzik, but...
> The MM layer is just "another module".
In theory. In practice our current build process in mm/ is not
compiled as a module. eg: if we put in mm/readahead.c
module_param(debug, int, 0600);
It'd be called "readahead.debug" not "mm.debug". Maybe that's fine,
but indicates the subtle difference.
> Also, can we please stop shouting? I'd much rather see
>
> module_param(debug, int, 0600)
Sure. MODULE_AUTHOR(), MODULE_DESCRIPTION(), MODULE_PARM_DESC() and
MODULE_LICENSE() fight the other way. They were previously module
only, but that's an implmentation detail: plan is to expose the first
three at least through sysfs, or just leave them as stubs for
documentation purposes.
Am off to visit Extremadura to see the LinEx project: will update
patch and re-send within 24 hrs,
Rusty.
--
Anyone who quotes me in their sig is an idiot. -- Rusty Russell.
next prev parent reply other threads:[~2002-11-17 18:15 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
2002-11-17 18:00 ` Linus Torvalds
2002-11-17 18:21 ` Rusty Russell [this message]
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=20021117182227.82F332C059@lists.samba.org \
--to=rusty@rustcorp.com.au \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@transmeta.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