From: Jesse Barnes <jbarnes@sgi.com>
To: linux-ia64@vger.kernel.org
Subject: Re: [Linux-ia64] [trivial] Request for merging of two sets of redundant SGI IA64 Configure.help text
Date: Mon, 09 Sep 2002 22:54:28 +0000 [thread overview]
Message-ID: <marc-linux-ia64-105590701906018@msgid-missing> (raw)
In-Reply-To: <marc-linux-ia64-105590701906017@msgid-missing>
You can just go ahead and delete the second version of each of the
options if you'd like.
Thanks,
Jesse
On Mon, Sep 09, 2002 at 04:01:21PM -0600, Steven Cole wrote:
> Greetings,
>
> Could one of you help resolve the following very trivial problem. In
> 2.4.20-pre5 Documentation/Configure.help, there exists two
> Configure.help entries for CONFIG_IA64_SGI_SN_SIM and
> CONFIG_IA64_SGI_SN_DEBUG.
>
> The configurators will of course only display the first of the two.
> Would someone please indicate which of the texts is the more accurate or
> combine them as you see fit. You can send me the results or make up a
> patch yourself.
>
> If this is a moot point, deleting the second text would be the default
> thing to do.
>
> Thanks,
> Steven
> (Configure.help maintainer)
>
> 1st text for CONFIG_IA64_SGI_SN_SIM:
>
> CONFIG_IA64_SGI_SN_SIM
> Build a kernel that runs on both the SGI simulator AND on hardware.
> There is a very slight performance penalty on hardware for including this
> option.
>
> 2nd text for CONFIG_IA64_SGI_SN_SIM:
>
> Enable SGI Medusa Simulator Support
> CONFIG_IA64_SGI_SN_SIM
> If you are compiling a kernel that will run under SGI's IA64
> simulator (Medusa) then say Y, otherwise say N.
>
> --------------------------------------------------------------------------
>
> 1st text for CONFIG_IA64_SGI_SN_DEBUG:
>
> CONFIG_IA64_SGI_SN_DEBUG
> This enables addition debug code that helps isolate
> platform/kernel bugs. There is a small but measurable performance
> degradation when this option is enabled.
>
> 2nd text for CONFIG_IA64_SGI_SN_DEBUG:
>
> Enable SGI SN extra debugging code
> CONFIG_IA64_SGI_SN_DEBUG
> Turns on extra debugging code in the SGI SN (Scalable NUMA) platform
> for IA64. Unless you are debugging problems on an SGI SN IA64 box,
> say N.
>
>
>
>
> _______________________________________________
> Linux-IA64 mailing list
> Linux-IA64@linuxia64.org
> http://lists.linuxia64.org/lists/listinfo/linux-ia64
next prev parent reply other threads:[~2002-09-09 22:54 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-09-09 22:01 [Linux-ia64] [trivial] Request for merging of two sets of redundant SGI IA64 Steven Cole
2002-09-09 22:54 ` Jesse Barnes [this message]
2002-09-11 5:51 ` [Linux-ia64] [trivial] Request for merging of two sets of redundant SGI IA64Configure.help texts Keith Owens
2002-09-12 2:32 ` [Linux-ia64] [trivial] Request for merging of two sets of Steven Cole
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=marc-linux-ia64-105590701906018@msgid-missing \
--to=jbarnes@sgi.com \
--cc=linux-ia64@vger.kernel.org \
/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