From: Jan-Benedict Glaw <jbglaw@lug-owl.de>
To: Linus Torvalds <torvalds@transmeta.com>
Cc: linux-kernel@vger.kernel.org
Subject: [Docu-PATCH] Updated docu for srm_env.o driver
Date: Wed, 5 Jun 2002 13:03:53 +0200 [thread overview]
Message-ID: <20020605110352.GP20788@lug-owl.de> (raw)
[-- Attachment #1: Type: text/plain, Size: 1460 bytes --]
Hi Linus!
Please apply this patch. It updates the documentation to my driver.
MfG, JBG
--- linux-2.5.20/arch/alpha/Config.help.orig Wed Jun 5 12:48:39 2002
+++ linux-2.5.20/arch/alpha/Config.help Wed Jun 5 12:58:54 2002
@@ -570,13 +570,14 @@
unless you really know what this hack does.
CONFIG_SRM_ENV
- If you enable this option, a subdirectory called srm_environment
- will give you access to the most important SRM environment
- variables. If you've got an Alpha style system supporting
- SRC, then it is a good idea to say Yes or Module to this driver.
+ If you enable this option, you'll find all important SRM environment
+ variables in /proc/srm_environment/named_variables/. In addition to
+ this, you can access any custom variable through its assigned number
+ in /proc/srm_environment/numbered_variables/. If you want to access
+ your SRM environment (or if you're building a generic kernel for
+ distribution) it's a good idea to say Y or M to this driver.
- This driver is also available as a module and will be called
- srm_env.o if you build it as a module.
+ If you build it as a module, the resulting file will be srm_env.o.
CONFIG_DEBUG_KERNEL
Say Y here if you are developing drivers or trying to debug and
--
Jan-Benedict Glaw . jbglaw@lug-owl.de . +49-172-7608481
-- New APT-Proxy written in shell script --
http://lug-owl.de/~jbglaw/software/ap2/
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
next reply other threads:[~2002-06-05 11:03 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-06-05 11:03 Jan-Benedict Glaw [this message]
2002-06-06 23:38 ` [Docu-PATCH] Updated docu for srm_env.o driver Ruth Ivimey-Cook
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=20020605110352.GP20788@lug-owl.de \
--to=jbglaw@lug-owl.de \
--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