From: Steven Cole <elenstev@mesatop.com>
To: Richard Henderson <rth@twiddle.net>
Cc: Linux Kernel <linux-kernel@vger.kernel.org>,
Linus Torvalds <torvalds@transmeta.com>,
Dave Jones <davej@suse.de>
Subject: [PATCH] 2.5.31 add three help texts to arch/alpha/Config.help
Date: 12 Aug 2002 10:38:21 -0600 [thread overview]
Message-ID: <1029170301.2045.23.camel@spc9.esa.lanl.gov> (raw)
This adds help texts to arch/alpha/Config.help for
CONFIG_ALPHA_EV67, CONFIG_DEBUG_RWLOCK and CONFIG_DEBUG_SEMAPHORE.
This has been in the -dj tree since about 2.5.7.
The texts were obtained from ESR's v2.97 Configure.help.
Steven
--- linux-2.5.31/arch/alpha/Config.help.orig Sat Aug 10 19:41:20 2002
+++ linux-2.5.31/arch/alpha/Config.help Mon Aug 12 09:52:42 2002
@@ -251,6 +251,10 @@
CONFIG_ALPHA_GAMMA
Say Y if you have an AS 2000 5/xxx or an AS 2100 5/xxx.
+CONFIG_ALPHA_EV67
+ Is this a machine based on the EV67 core? If in doubt, select N here
+ and the machine will be treated as an EV6.
+
CONFIG_ALPHA_SRM
There are two different types of booting firmware on Alphas: SRM,
which is command line driven, and ARC, which uses menus and arrow
@@ -598,4 +602,15 @@
and certain other kinds of spinlock errors commonly made. This is
best used in conjunction with the NMI watchdog so that spinlock
deadlocks are also debuggable.
+
+CONFIG_DEBUG_RWLOCK
+ If you say Y here then read-write lock processing will count how many
+ times it has tried to get the lock and issue an error message after
+ too many attempts. If you suspect a rwlock problem or a kernel
+ hacker asks for this option then say Y. Otherwise say N.
+
+CONFIG_DEBUG_SEMAPHORE
+ If you say Y here then semaphore processing will issue lots of
+ verbose debugging messages. If you suspect a semaphore problem or a
+ kernel hacker asks for this option then say Y. Otherwise say N.
reply other threads:[~2002-08-12 16:37 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=1029170301.2045.23.camel@spc9.esa.lanl.gov \
--to=elenstev@mesatop.com \
--cc=davej@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=rth@twiddle.net \
--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;
as well as URLs for NNTP newsgroup(s).