From: Rusty Russell <rusty@rustcorp.com.au>
To: Matthew Wilcox <willy@debian.org>
Cc: jgarzik@redhat.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Module parameters reimplementation 0/4
Date: Fri, 15 Nov 2002 04:33:37 +1100 [thread overview]
Message-ID: <20021114174310.9DD642C2A7@lists.samba.org> (raw)
In-Reply-To: Your message of "Thu, 14 Nov 2002 12:39:40 -0000." <20021114123940.U30392@parcelfarce.linux.theplanet.co.uk>
In message <20021114123940.U30392@parcelfarce.linux.theplanet.co.uk> you write:
> Rusty wrote:
> > Jgarzik wrote:
> > > Let's be more friendly to the namespace and call it something less
> > > ambiguous, like MODULE_PARAM, even if that might not be strictly true in
> > > 1% of the cases. IMO there are certainly valid local uses of 'PARAM' in
> > > kernel code.
> >
> > I disagree. It's a param, subsuming both __setup and MODULE_PARAM.
> > The fact that it is implemented for modules is not something for the
> > driver author to be concerned about (finally).
>
> You're both wrong ;-) `module' != `loadable module'.
Now we're descending into sophistry. But PARAM() is useful in (say)
init/main.c, as well, and it's a stretch to call it a module...
Rusty.
--
Anyone who quotes me in their sig is an idiot. -- Rusty Russell.
next prev parent reply other threads:[~2002-11-14 17:36 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-11-14 12:39 [PATCH] Module parameters reimplementation 0/4 Matthew Wilcox
2002-11-14 17:33 ` Rusty Russell [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-11-14 4:23 Rusty Russell
2002-11-14 4:16 ` Jeff Garzik
2002-11-14 5:45 ` Rusty Russell
2002-11-14 15:03 ` Andrey Panin
2002-11-14 17:35 ` Rusty Russell
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=20021114174310.9DD642C2A7@lists.samba.org \
--to=rusty@rustcorp.com.au \
--cc=jgarzik@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=willy@debian.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