The patch titled
kconfig: remove leading whitespace in menu prompts
has been removed from the -mm tree. Its filename is
kconfig-remove-leading-whitespace-in-menu-prompts.patch
This patch was dropped because it was merged into mainline or a subsystem tree
------------------------------------------------------
Subject: kconfig: remove leading whitespace in menu prompts
From: Roman Zippel <zippel@xxxxxxxxxxxxxx>
This removes all the leading whitespace kconfig now warns about.
Signed-off-by: Roman Zippel <zippel@xxxxxxxxxxxxxx>
Cc: Sam Ravnborg <sam@xxxxxxxxxxxx>
Signed-off-by: Andrew Morton <akpm@xxxxxxxx>
---
drivers/mtd/Kconfig | 4 ++--
drivers/mtd/maps/Kconfig | 2 +-
drivers/scsi/Kconfig | 10 +++++-----
sound/oss/Kconfig | 2 +-
scsi/qla2xxx/Kconfig | 0
5 files changed, 9 insertions(+), 9 deletions(-)
diff -puN drivers/mtd/Kconfig~kconfig-remove-leading-whitespace-in-menu-prompts drivers/mtd/Kconfig
--- devel/drivers/mtd/Kconfig~kconfig-remove-leading-whitespace-in-menu-prompts 2006-05-24 12:03:38.000000000 -0700
+++ devel-akpm/drivers/mtd/Kconfig 2006-05-24 12:03:38.000000000 -0700
@@ -86,14 +86,14 @@ config MTD_REDBOOT_DIRECTORY_BLOCK
block and "-2" means the penultimate block.
config MTD_REDBOOT_PARTS_UNALLOCATED
- bool " Include unallocated flash regions"
+ bool "Include unallocated flash regions"
depends on MTD_REDBOOT_PARTS
help
If you need to register each unallocated flash region as a MTD
'partition', enable this option.
config MTD_REDBOOT_PARTS_READONLY
- bool " Force read-only for RedBoot system images"
+ bool "Force read-only for RedBoot system images"
depends on MTD_REDBOOT_PARTS
help
If you need to force read-only for 'RedBoot', 'RedBoot Config' and
diff -puN drivers/mtd/maps/Kconfig~kconfig-remove-leading-whitespace-in-menu-prompts drivers/mtd/maps/Kconfig
--- devel/drivers/mtd/maps/Kconfig~kconfig-remove-leading-whitespace-in-menu-prompts 2006-05-24 12:03:38.000000000 -0700
+++ devel-akpm/drivers/mtd/maps/Kconfig 2006-05-24 12:03:38.000000000 -0700
@@ -212,7 +212,7 @@ config MTD_NETtel
Support for flash chips on NETtel/SecureEdge/SnapGear boards.
config MTD_ALCHEMY
- tristate ' AMD Alchemy Pb1xxx/Db1xxx/RDK MTD support'
+ tristate "AMD Alchemy Pb1xxx/Db1xxx/RDK MTD support"
depends on SOC_AU1X00
help
Flash memory access on AMD Alchemy Pb/Db/RDK Reference Boards
diff -puN drivers/scsi/Kconfig~kconfig-remove-leading-whitespace-in-menu-prompts drivers/scsi/Kconfig
--- devel/drivers/scsi/Kconfig~kconfig-remove-leading-whitespace-in-menu-prompts 2006-05-24 12:03:38.000000000 -0700
+++ devel-akpm/drivers/scsi/Kconfig 2006-05-24 12:03:38.000000000 -0700
@@ -1159,7 +1159,7 @@ config SCSI_NCR_Q720
you do not have this SCSI card, so say N.
config SCSI_NCR53C8XX_DEFAULT_TAGS
- int " default tagged command queue depth"
+ int "default tagged command queue depth"
depends on SCSI_ZALON || SCSI_NCR_Q720
default "8"
---help---
@@ -1185,7 +1185,7 @@ config SCSI_NCR53C8XX_DEFAULT_TAGS
There is no safe option other than using good SCSI devices.
config SCSI_NCR53C8XX_MAX_TAGS
- int " maximum number of queued commands"
+ int "maximum number of queued commands"
depends on SCSI_ZALON || SCSI_NCR_Q720
default "32"
---help---
@@ -1202,7 +1202,7 @@ config SCSI_NCR53C8XX_MAX_TAGS
There is no safe option and the default answer is recommended.
config SCSI_NCR53C8XX_SYNC
- int " synchronous transfers frequency in MHz"
+ int "synchronous transfers frequency in MHz"
depends on SCSI_ZALON || SCSI_NCR_Q720
default "20"
---help---
@@ -1236,7 +1236,7 @@ config SCSI_NCR53C8XX_SYNC
terminations and SCSI conformant devices.
config SCSI_NCR53C8XX_PROFILE
- bool " enable profiling"
+ bool "enable profiling"
depends on SCSI_ZALON || SCSI_NCR_Q720
help
This option allows you to enable profiling information gathering.
@@ -1247,7 +1247,7 @@ config SCSI_NCR53C8XX_PROFILE
The normal answer therefore is N.
config SCSI_NCR53C8XX_NO_DISCONNECT
- bool " not allow targets to disconnect"
+ bool "not allow targets to disconnect"
depends on (SCSI_ZALON || SCSI_NCR_Q720) && SCSI_NCR53C8XX_DEFAULT_TAGS=0
help
This option is only provided for safety if you suspect some SCSI
diff -puN drivers/scsi/qla2xxx/Kconfig~kconfig-remove-leading-whitespace-in-menu-prompts drivers/scsi/qla2xxx/Kconfig
diff -puN sound/oss/Kconfig~kconfig-remove-leading-whitespace-in-menu-prompts sound/oss/Kconfig
--- devel/sound/oss/Kconfig~kconfig-remove-leading-whitespace-in-menu-prompts 2006-05-24 12:03:38.000000000 -0700
+++ devel-akpm/sound/oss/Kconfig 2006-05-24 12:03:38.000000000 -0700
@@ -838,6 +838,6 @@ config SOUND_SH_DAC_AUDIO
depends on SOUND_PRIME && CPU_SH3
config SOUND_SH_DAC_AUDIO_CHANNEL
- int " DAC channel"
+ int "DAC channel"
default "1"
depends on SOUND_SH_DAC_AUDIO
_
Patches currently in -mm which might be from zippel@xxxxxxxxxxxxxx are
git-kbuild.patch
m68k-completely-initialize-hw_regs_t-in-ide_setup_ports.patch
m68k-atyfb_base-compile-fix-for-config_pci=n.patch
m68k-cleanup-unistdh.patch
m68k-remove-some-unused-definitions-in-zorroh.patch
m68k-use-c99-initializer.patch
m68k-print-correct-stack-trace.patch
m68k-restore-amikbd-compatibility-with-24.patch
m68k-extra-delay.patch
m68k-use-proper-defines-for-zone-initialization.patch
m68k-adjust-to-changed-hardirq_mask.patch
m68k-m68k-mac-via2-fixes-and-cleanups.patch
m68k-clean-up-uaccessh.patch
fix-incorrect-sa_onstack-behaviour-for-64-bit-processes.patch
adjust-handle_irr_event-return-type.patch
time-use-clocksource-abstraction-for-ntp-adjustments-optimize-out-some-mults-since-gcc-cant-avoid-them.patch
time-rename-clocksource-functions.patch
fix-rt-mutex-defaults-and-dependencies.patch
-
To unsubscribe from this list: send the line "unsubscribe mm-commits" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
