summaryrefslogtreecommitdiffstats
path: root/arch/m68k
diff options
context:
space:
mode:
authorDave Hansen <haveblue@us.ibm.com>2005-06-23 00:07:43 -0700
committerLinus Torvalds <torvalds@ppc970.osdl.org>2005-06-23 09:45:02 -0700
commit3f22ab276b931b72ea04b184c155b34d0362bfc3 (patch)
tree013e6ba32f4b2fcb66f9726ba6b2c6dc64f6622d /arch/m68k
parent3a9da7655d2d5b7f790a370328cf093440c80496 (diff)
downloadkernel-crypto-3f22ab276b931b72ea04b184c155b34d0362bfc3.tar.gz
kernel-crypto-3f22ab276b931b72ea04b184c155b34d0362bfc3.tar.xz
kernel-crypto-3f22ab276b931b72ea04b184c155b34d0362bfc3.zip
[PATCH] make each arch use mm/Kconfig
For all architectures, this just means that you'll see a "Memory Model" choice in your architecture menu. For those that implement DISCONTIGMEM, you may eventually want to make your ARCH_DISCONTIGMEM_ENABLE a "def_bool y" and make your users select DISCONTIGMEM right out of the new choice menu. The only disadvantage might be if you have some specific things that you need in your help option to explain something about DISCONTIGMEM. Signed-off-by: Dave Hansen <haveblue@us.ibm.com> Signed-off-by: Adrian Bunk <bunk@stusta.de> Signed-off-by: Andrew Morton <akpm@osdl.org> Signed-off-by: Linus Torvalds <torvalds@osdl.org>
Diffstat (limited to 'arch/m68k')
-rw-r--r--arch/m68k/Kconfig2
1 files changed, 2 insertions, 0 deletions
diff --git a/arch/m68k/Kconfig b/arch/m68k/Kconfig
index d0713c7d9f0..691a2469ff3 100644
--- a/arch/m68k/Kconfig
+++ b/arch/m68k/Kconfig
@@ -357,6 +357,8 @@ config 060_WRITETHROUGH
is hardwired on. The 53c710 SCSI driver is known to suffer from
this problem.
+source "mm/Kconfig"
+
endmenu
menu "General setup"