From: "Randy.Dunlap" <rddunlap@osdl.org>
To: rusty@rustcorp.com.au, akpm <akpm@osdl.org>
Cc: lkml <linux-kernel@vger.kernel.org>
Subject: [PATCH] doc: specifiying module parameters
Date: Mon, 26 Apr 2004 20:57:11 -0700 [thread overview]
Message-ID: <20040426205711.64b7e72c.rddunlap@osdl.org> (raw)
// linux-266-rc2
// kernel-parameters.txt doc. only: add info on how to specify
// loadable module parameters vs. built-in module parameters
diffstat:=
Documentation/kernel-parameters.txt | 11 +++++++++++
1 files changed, 11 insertions(+)
diff -Naurp ./Documentation/kernel-parameters.txt~doc_module_prms ./Documentation/kernel-parameters.txt
--- ./Documentation/kernel-parameters.txt~doc_module_prms 2004-04-03 19:38:27.000000000 -0800
+++ ./Documentation/kernel-parameters.txt 2004-04-26 20:06:31.000000000 -0700
@@ -6,6 +6,17 @@ The following is a consolidated list of
(defined as ignoring all punctuation and sorting digits before letters in a
case insensitive manner), and with descriptions where known.
+Module parameters for loadable modules are specified only as the
+parameter name with optional '=' and value as appropriate, such as:
+
+ modprobe usbcore blinkenlights=1
+
+Module parameters for modules that are built into the kernel image
+are specified on the kernel command line with the module name plus
+'.' plus parameter name, with '=' and value if appropriate, such as:
+
+ usbcore.blinkenlights=1
+
The text in square brackets at the beginning of the description state the
restrictions on the kernel for the said kernel parameter to be valid. The
restrictions referred to are that the relevant option is valid if:
--
reply other threads:[~2004-04-27 3:58 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20040426205711.64b7e72c.rddunlap@osdl.org \
--to=rddunlap@osdl.org \
--cc=akpm@osdl.org \
--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
all inboxes | Powered by JetHome®