From: Keith Owens <kaos@ocs.com.au>
To: Russell King <rmk@arm.linux.org.uk>
Cc: Werner.Almesberger@epfl.ch (Werner Almesberger),
david_luyer@pacific.net.au (David Luyer),
alan@redhat.com, linux-kernel@vger.kernel.org
Subject: Re: PATCH: "Pass module parameters" to built-in drivers
Date: Tue, 23 Jan 2001 17:37:02 +1100 [thread overview]
Message-ID: <22446.980231822@ocs3.ocs-net> (raw)
In-Reply-To: Your message of "Mon, 22 Jan 2001 21:55:23 -0000." <200101222155.f0MLtNe01781@flint.arm.linux.org.uk>
On Mon, 22 Jan 2001 21:55:23 +0000 (GMT),
Russell King <rmk@arm.linux.org.uk> wrote:
>Hmm, don't we already have all that __setup() stuff laying around? Ok,
>it might not be built into the .o for modules, but it could be. Could
>we not do something along the lines of:
>
>1. User passes parameters on the kernel command line.
>2. modprobe reads the kernel command line and sorts out those that
> correspond to the __setup() stuff in the module being loaded.
>3. modprobe combines in any extra settings from /etc/modules.conf
>
>IIRC, this would satisfy the original posters intentions, presumably
>without too much hastle?
Apart from the fact that it is completely backwards from the original
intent. The problem is objects that have MODULE_PARM but no __setup.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
next prev parent reply other threads:[~2001-01-23 6:37 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-21 4:54 PATCH: "Pass module parameters" to built-in drivers David Luyer
2001-01-21 5:09 ` Keith Owens
2001-01-22 15:56 ` Werner Almesberger
2001-01-22 16:30 ` Keith Owens
2001-01-22 18:08 ` Werner Almesberger
2001-01-22 21:55 ` Russell King
2001-01-23 6:37 ` Keith Owens [this message]
2001-01-23 9:18 ` Richard Guenther
2001-01-24 13:32 ` Paul Gortmaker
2001-01-24 20:57 ` Keith Owens
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=22446.980231822@ocs3.ocs-net \
--to=kaos@ocs.com.au \
--cc=Werner.Almesberger@epfl.ch \
--cc=alan@redhat.com \
--cc=david_luyer@pacific.net.au \
--cc=linux-kernel@vger.kernel.org \
--cc=rmk@arm.linux.org.uk \
/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