From: Dave Hansen <dave@sr71.net>
To: linux-kernel@vger.kernel.org
Cc: x86@kernel.org, Dave Hansen <dave@sr71.net>
Subject: [PATCH 09/12] x86 Kconfig: create mtrr menu
Date: Mon, 30 Dec 2013 10:40:58 -0800 [thread overview]
Message-ID: <20131230184058.0A59E033@viggo.jf.intel.com> (raw)
In-Reply-To: <20131230184046.F5E42919@viggo.jf.intel.com>
From: Dave Hansen <dave.hansen@linux.intel.com>
This removes another 4 lines from the default x86 menu. Note
that I slightly changed the MTRR prompt text since PAT is
hidden under here. This makes PAT easier to find since it
"depends on MTRR" anyway.
Signed-off-by: Dave Hansen <dave.hansen@linux.intel.com>
---
linux.git-davehans/arch/x86/Kconfig | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff -puN arch/x86/Kconfig~x86-mtrr-menu arch/x86/Kconfig
--- linux.git/arch/x86/Kconfig~x86-mtrr-menu 2013-12-30 10:37:45.990268296 -0800
+++ linux.git-davehans/arch/x86/Kconfig 2013-12-30 10:37:45.995268521 -0800
@@ -1387,9 +1387,9 @@ config MATH_EMULATION
If you are not sure, say Y; apart from resulting in a 66 KB bigger
kernel, it won't hurt.
-config MTRR
+menuconfig MTRR
def_bool y
- prompt "MTRR (Memory Type Range Register) support" if EXPERT
+ prompt "MTRR (Memory Type Range Register) and PAT support" if EXPERT
---help---
On Intel P6 family processors (Pentium Pro, Pentium II and later)
the Memory Type Range Registers (MTRRs) may be used to control
_
next prev parent reply other threads:[~2013-12-30 18:41 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-30 18:40 [PATCH 00/12] Reorganize x86 Kconfig menu Dave Hansen
2013-12-30 18:40 ` [PATCH 01/12] x86 Kconfig: create extended platforms menu Dave Hansen
2013-12-31 19:26 ` Randy Dunlap
2013-12-31 20:07 ` Dave Hansen
2013-12-30 18:40 ` [PATCH 02/12] x86 Kconfig: memory options Dave Hansen
2013-12-30 18:40 ` [PATCH 03/12] x86 Kconfig: move highmem Dave Hansen
2013-12-30 18:40 ` [PATCH 04/12] x86 Kconfig: processor options menu Dave Hansen
2013-12-30 18:40 ` [PATCH 05/12] x86 Kconfig: processor drivers Dave Hansen
2013-12-30 18:40 ` [PATCH 06/12] x86 Kconfig: scheduler options Dave Hansen
2013-12-30 18:40 ` [PATCH 07/12] x86 Kconfig: move memtest Dave Hansen
2013-12-30 18:40 ` [PATCH 08/12] x86 Kconfig: bury obscure options Dave Hansen
2013-12-30 18:40 ` Dave Hansen [this message]
2013-12-31 19:26 ` [PATCH 09/12] x86 Kconfig: create mtrr menu Randy Dunlap
2013-12-31 20:06 ` Dave Hansen
2013-12-30 18:40 ` [PATCH 10/12] x86 Kconfig: MCE menu Dave Hansen
2013-12-30 18:41 ` [PATCH 11/12] x86 Kconfig: move paravirt under virtualization Dave Hansen
2013-12-30 18:41 ` [PATCH 12/12] x86 Kconfig: move paravirt under "Virtualization" Dave Hansen
2013-12-31 19:40 ` [PATCH 00/12] Reorganize x86 Kconfig menu Randy Dunlap
2013-12-31 20:24 ` Dave Hansen
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=20131230184058.0A59E033@viggo.jf.intel.com \
--to=dave@sr71.net \
--cc=linux-kernel@vger.kernel.org \
--cc=x86@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
Powered by JetHome