From: Stefan Richter <stefanr@s5r6.in-berlin.de>
To: linux-kernel@vger.kernel.org
Cc: Randy Dunlap <rdunlap@xenotime.net>
Subject: [PATCH 2/3] Doc/kernel-parameters.txt: mention modinfo and sysfs
Date: Mon, 13 Mar 2006 20:22:04 +0100 (CET) [thread overview]
Message-ID: <tkrat.fb495404c563eaf7@s5r6.in-berlin.de> (raw)
In-Reply-To: <tkrat.f6b9032d78fc1d70@s5r6.in-berlin.de>
Doc/kernel-parameters.txt: mention modinfo and sysfs
Signed-off-by: Stefan Richter <stefanr@s5r6.in-berlin.de>
--- linux/Documentation/kernel-parameters.txt.1 2006-03-13 19:32:28.000000000 +0100
+++ linux/Documentation/kernel-parameters.txt 2006-03-13 19:57:52.000000000 +0100
@@ -17,6 +17,13 @@
usbcore.blinkenlights=1
+This document may not be entirely up to date and comprehensive. The command
+"modinfo -p ${modulename}" shows a current list of all parameters of a loadable
+module. Loadable modules, after being loaded into the running kernel, also
+reveal their parameters in /sys/module/${modulename}/parameters/. Some of these
+parameters may be changed at runtime by the command
+"echo -n ${value} > /sys/module/${modulename}/parameters/${parm}".
+
The text in square brackets at the beginning of the description states 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:
next prev parent reply other threads:[~2006-03-13 19:25 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-13 19:21 [PATCH 1/3] Doc/kernel-parameters.txt: delete false version information and history Stefan Richter
2006-03-13 19:22 ` Stefan Richter [this message]
2006-03-13 19:23 ` [PATCH 3/3] Doc/kernel-parameters.txt: slightly reword sentence about restrictions Stefan Richter
2006-03-13 19:35 ` Randy.Dunlap
2006-03-13 19:40 ` Stefan Richter
2006-03-13 19:32 ` [PATCH 1/3] Doc/kernel-parameters.txt: delete false version information and history Randy.Dunlap
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=tkrat.fb495404c563eaf7@s5r6.in-berlin.de \
--to=stefanr@s5r6.in-berlin.de \
--cc=linux-kernel@vger.kernel.org \
--cc=rdunlap@xenotime.net \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.