From: Adrian Bunk <bunk@stusta.de>
To: rmk@arm.linux.org.uk
Cc: linux-kernel@vger.kernel.org, dwmw2@infradead.org,
linux-mtd@lists.infradead.org
Subject: [RFC: 2.6 patch] let arm use drivers/Kconfig
Date: Mon, 17 Apr 2006 16:48:23 +0200 [thread overview]
Message-ID: <20060417144823.GC7429@stusta.de> (raw)
This patch lets arm use drivers/Kconfig.
Signed-off-by: Adrian Bunk <bunk@stusta.de>
---
arch/arm/Kconfig | 75 --------------------------------------------
drivers/Kconfig | 2 +
drivers/mtd/Kconfig | 1
3 files changed, 4 insertions(+), 74 deletions(-)
--- linux-2.6.17-rc1-mm2-arm/arch/arm/Kconfig.old 2006-04-17 14:25:08.000000000 +0200
+++ linux-2.6.17-rc1-mm2-arm/arch/arm/Kconfig 2006-04-17 14:54:15.000000000 +0200
@@ -794,80 +794,7 @@
source "net/Kconfig"
-menu "Device Drivers"
-
-source "drivers/base/Kconfig"
-
-source "drivers/connector/Kconfig"
-
-if ALIGNMENT_TRAP
-source "drivers/mtd/Kconfig"
-endif
-
-source "drivers/parport/Kconfig"
-
-source "drivers/pnp/Kconfig"
-
-source "drivers/block/Kconfig"
-
-source "drivers/acorn/block/Kconfig"
-
-if PCMCIA || ARCH_CLPS7500 || ARCH_IOP3XX || ARCH_IXP4XX \
- || ARCH_L7200 || ARCH_LH7A40X || ARCH_PXA || ARCH_RPC \
- || ARCH_S3C2410 || ARCH_SA1100 || ARCH_SHARK || FOOTBRIDGE \
- || ARCH_IXP23XX
-source "drivers/ide/Kconfig"
-endif
-
-source "drivers/scsi/Kconfig"
-
-source "drivers/md/Kconfig"
-
-source "drivers/message/fusion/Kconfig"
-
-source "drivers/ieee1394/Kconfig"
-
-source "drivers/message/i2o/Kconfig"
-
-source "drivers/net/Kconfig"
-
-source "drivers/isdn/Kconfig"
-
-# input before char - char/joystick depends on it. As does USB.
-
-source "drivers/input/Kconfig"
-
-source "drivers/char/Kconfig"
-
-source "drivers/i2c/Kconfig"
-
-source "drivers/spi/Kconfig"
-
-source "drivers/w1/Kconfig"
-
-source "drivers/hwmon/Kconfig"
-
-#source "drivers/l3/Kconfig"
-
-source "drivers/misc/Kconfig"
-
-source "drivers/mfd/Kconfig"
-
-source "drivers/leds/Kconfig"
-
-source "drivers/media/Kconfig"
-
-source "drivers/video/Kconfig"
-
-source "sound/Kconfig"
-
-source "drivers/usb/Kconfig"
-
-source "drivers/mmc/Kconfig"
-
-source "drivers/rtc/Kconfig"
-
-endmenu
+source "drivers/Kconfig"
source "fs/Kconfig"
--- linux-2.6.17-rc1-mm2-arm/drivers/mtd/Kconfig.old 2006-04-17 14:32:35.000000000 +0200
+++ linux-2.6.17-rc1-mm2-arm/drivers/mtd/Kconfig 2006-04-17 15:00:57.000000000 +0200
@@ -1,6 +1,7 @@
# $Id: Kconfig,v 1.11 2005/11/07 11:14:19 gleixner Exp $
menu "Memory Technology Devices (MTD)"
+ depends on (ALIGNMENT_TRAP || !ARM)
config MTD
tristate "Memory Technology Device (MTD) support"
--- linux-2.6.17-rc1-mm2-arm/drivers/Kconfig.old 2006-04-17 14:51:25.000000000 +0200
+++ linux-2.6.17-rc1-mm2-arm/drivers/Kconfig 2006-04-17 14:51:38.000000000 +0200
@@ -14,6 +14,8 @@
source "drivers/block/Kconfig"
+source "drivers/acorn/block/Kconfig"
+
source "drivers/ide/Kconfig"
source "drivers/scsi/Kconfig"
next reply other threads:[~2006-04-17 14:48 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-17 14:48 Adrian Bunk [this message]
2006-04-17 14:55 ` [RFC: 2.6 patch] let arm use drivers/Kconfig David Woodhouse
2006-04-20 12:06 ` Adrian Bunk
2006-04-20 20:54 ` David Woodhouse
2006-04-21 9:32 ` Jörn Engel
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=20060417144823.GC7429@stusta.de \
--to=bunk@stusta.de \
--cc=dwmw2@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mtd@lists.infradead.org \
--cc=rmk@arm.linux.org.uk \
/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