[PATCH] [RESEND] score: Kconfig: drop nine selects and one entry
The config entries in the "System type" choice each use the same three select statements. The Kconfig symbol SYS_SUPPORTS_32BIT_KERNEL is only used by mips. The Kconfig symbol CPU_SCORE7 is used once, in an (almost) empty Kconfig entry, and there are no uses of CONFIG_CPU_SCORE7. (This means that the CPU_SCORE7 entry can also be dropped.) And GENERIC_HAS_IOMAP is a typo. It should have been GENERIC_IOMAP. But there's an entry for GENERIC_IOMAP that defaults to y, so no one noticed. So all selects from the config entries in this choice can be dropped. And so can the CPU_SCORE7 config entry. Signed-off-by: Paul Bolle --- 0) This patch was first sent over a year ago. Now I have reapplied it on top of v3.9-rc1, which required a trivial adaption to context changes. 1) Still git grep tested only. 2) Please note that ARCH_SCORE7, MACH_SPCT6600, and SCORE_SIM still aren't used anywhere else. There are also no uses of CONFIG_ARCH_SCORE7, CONFIG_MACH_SPCT6600, and CONFIG_SCORE_SIM macros. Perhaps the entire "System type" choice can be dropped. arch/score/Kconfig | 13 + 1 file changed, 1 insertion(+), 12 deletions(-) diff --git a/arch/score/Kconfig b/arch/score/Kconfig index e569aa1..382b996 100644 --- a/arch/score/Kconfig +++ b/arch/score/Kconfig @@ -22,28 +22,17 @@ choice config ARCH_SCORE7 bool "SCORE7 processor" - select SYS_SUPPORTS_32BIT_KERNEL - select CPU_SCORE7 - select GENERIC_HAS_IOMAP config MACH_SPCT6600 bool "SPCT6600 series based machines" - select SYS_SUPPORTS_32BIT_KERNEL - select CPU_SCORE7 - select GENERIC_HAS_IOMAP config SCORE_SIM bool "Score simulator" - select SYS_SUPPORTS_32BIT_KERNEL - select CPU_SCORE7 - select GENERIC_HAS_IOMAP + endchoice endmenu -config CPU_SCORE7 - bool - config NO_DMA bool default y -- 1.7.11.7 -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
[PATCH] [RESEND] score: Kconfig: drop nine selects and one entry
The config entries in the System type choice each use the same three select statements. The Kconfig symbol SYS_SUPPORTS_32BIT_KERNEL is only used by mips. The Kconfig symbol CPU_SCORE7 is used once, in an (almost) empty Kconfig entry, and there are no uses of CONFIG_CPU_SCORE7. (This means that the CPU_SCORE7 entry can also be dropped.) And GENERIC_HAS_IOMAP is a typo. It should have been GENERIC_IOMAP. But there's an entry for GENERIC_IOMAP that defaults to y, so no one noticed. So all selects from the config entries in this choice can be dropped. And so can the CPU_SCORE7 config entry. Signed-off-by: Paul Bolle pebo...@tiscali.nl --- 0) This patch was first sent over a year ago. Now I have reapplied it on top of v3.9-rc1, which required a trivial adaption to context changes. 1) Still git grep tested only. 2) Please note that ARCH_SCORE7, MACH_SPCT6600, and SCORE_SIM still aren't used anywhere else. There are also no uses of CONFIG_ARCH_SCORE7, CONFIG_MACH_SPCT6600, and CONFIG_SCORE_SIM macros. Perhaps the entire System type choice can be dropped. arch/score/Kconfig | 13 + 1 file changed, 1 insertion(+), 12 deletions(-) diff --git a/arch/score/Kconfig b/arch/score/Kconfig index e569aa1..382b996 100644 --- a/arch/score/Kconfig +++ b/arch/score/Kconfig @@ -22,28 +22,17 @@ choice config ARCH_SCORE7 bool SCORE7 processor - select SYS_SUPPORTS_32BIT_KERNEL - select CPU_SCORE7 - select GENERIC_HAS_IOMAP config MACH_SPCT6600 bool SPCT6600 series based machines - select SYS_SUPPORTS_32BIT_KERNEL - select CPU_SCORE7 - select GENERIC_HAS_IOMAP config SCORE_SIM bool Score simulator - select SYS_SUPPORTS_32BIT_KERNEL - select CPU_SCORE7 - select GENERIC_HAS_IOMAP + endchoice endmenu -config CPU_SCORE7 - bool - config NO_DMA bool default y -- 1.7.11.7 -- To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
