forked from Minki/linux
treewide: Fix typos in Kconfig
This patch fixes some spelling typos found in Kconfig files. Signed-off-by: Masanari Iida <standby24x7@gmail.com> Acked-by: Randy Dunlap <rdunlap@infradead.org> Signed-off-by: Jiri Kosina <jkosina@suse.cz>
This commit is contained in:
parent
24d654fadd
commit
83fc61a563
@ -505,7 +505,7 @@ config ALPHA_QEMU
|
||||
|
||||
Generic kernels will auto-detect QEMU. But when building a
|
||||
system-specific kernel, the assumption is that we want to
|
||||
elimiate as many runtime tests as possible.
|
||||
eliminate as many runtime tests as possible.
|
||||
|
||||
If unsure, say N.
|
||||
|
||||
|
@ -298,7 +298,7 @@ config ARC_MMU_V1
|
||||
config ARC_MMU_V2
|
||||
bool "MMU v2"
|
||||
help
|
||||
Fixed the deficiency of v1 - possible thrashing in memcpy sceanrio
|
||||
Fixed the deficiency of v1 - possible thrashing in memcpy scenario
|
||||
when 2 D-TLB and 1 I-TLB entries index into same 2way set.
|
||||
|
||||
config ARC_MMU_V3
|
||||
@ -371,7 +371,7 @@ config ARC_FPU_SAVE_RESTORE
|
||||
bool "Enable FPU state persistence across context switch"
|
||||
default n
|
||||
help
|
||||
Double Precision Floating Point unit had dedictaed regs which
|
||||
Double Precision Floating Point unit had dedicated regs which
|
||||
need to be saved/restored across context-switch.
|
||||
Note that ARC FPU is overly simplistic, unlike say x86, which has
|
||||
hardware pieces to allow software to conditionally save/restore,
|
||||
@ -467,7 +467,7 @@ config ARC_PLAT_NEEDS_PHYS_TO_DMA
|
||||
bool
|
||||
|
||||
config ARC_KVADDR_SIZE
|
||||
int "Kernel Virtaul Address Space size (MB)"
|
||||
int "Kernel Virtual Address Space size (MB)"
|
||||
range 0 512
|
||||
default "256"
|
||||
help
|
||||
|
@ -22,7 +22,7 @@ config ARCH_BCM_IPROC
|
||||
help
|
||||
This enables support for systems based on Broadcom IPROC architected SoCs.
|
||||
The IPROC complex contains one or more ARM CPUs along with common
|
||||
core periperals. Application specific SoCs are created by adding a
|
||||
core peripherals. Application specific SoCs are created by adding a
|
||||
uArchitecture containing peripherals outside of the IPROC complex.
|
||||
Currently supported SoCs are Cygnus.
|
||||
|
||||
@ -68,8 +68,8 @@ config ARCH_BCM_5301X
|
||||
Support for Broadcom BCM470X and BCM5301X SoCs with ARM CPU cores.
|
||||
|
||||
This is a network SoC line mostly used in home routers and
|
||||
wifi access points, it's internal name is Northstar.
|
||||
This inclused the following SoC: BCM53010, BCM53011, BCM53012,
|
||||
wifi access points, its internal name is Northstar.
|
||||
This includes the following SoC: BCM53010, BCM53011, BCM53012,
|
||||
BCM53014, BCM53015, BCM53016, BCM53017, BCM53018, BCM4707,
|
||||
BCM4708 and BCM4709.
|
||||
|
||||
|
@ -278,7 +278,7 @@ config SAMSUNG_PM_CHECK_CHUNKSIZE
|
||||
help
|
||||
Set the chunksize in Kilobytes of the CRC for checking memory
|
||||
corruption over suspend and resume. A smaller value will mean that
|
||||
the CRC data block will take more memory, but wil identify any
|
||||
the CRC data block will take more memory, but will identify any
|
||||
faults with better precision.
|
||||
|
||||
See <file:Documentation/arm/Samsung-S3C24XX/Suspend.txt>
|
||||
|
@ -946,7 +946,7 @@ config ARM64_UAO
|
||||
help
|
||||
User Access Override (UAO; part of the ARMv8.2 Extensions)
|
||||
causes the 'unprivileged' variant of the load/store instructions to
|
||||
be overriden to be privileged.
|
||||
be overridden to be privileged.
|
||||
|
||||
This option changes get_user() and friends to use the 'unprivileged'
|
||||
variant of the load/store instructions. This ensures that user-space
|
||||
|
@ -78,7 +78,7 @@ config UDBG_RTAS_CONSOLE
|
||||
config PPC_SMP_MUXED_IPI
|
||||
bool
|
||||
help
|
||||
Select this opton if your platform supports SMP and your
|
||||
Select this option if your platform supports SMP and your
|
||||
interrupt controller provides less than 4 interrupts to each
|
||||
cpu. This will enable the generic code to multiplex the 4
|
||||
messages on to one ipi.
|
||||
|
@ -114,7 +114,7 @@ endif
|
||||
|
||||
source "arch/unicore32/mm/Kconfig"
|
||||
|
||||
comment "Floating poing support"
|
||||
comment "Floating point support"
|
||||
|
||||
config UNICORE_FPU_F64
|
||||
def_bool y if !ARCH_FPGA
|
||||
|
@ -223,7 +223,7 @@ config INITIALIZE_XTENSA_MMU_INSIDE_VMLINUX
|
||||
then enter your normal kernel breakpoints once the MMU was mapped
|
||||
to the kernel mappings (0XC0000000).
|
||||
|
||||
This unfortunately doesn't work for U-Boot and likley also wont
|
||||
This unfortunately won't work for U-Boot and likely also wont
|
||||
work for using KEXEC to have a hot kernel ready for doing a
|
||||
KDUMP.
|
||||
|
||||
|
@ -9,7 +9,7 @@ config NET_VENDOR_AQUANTIA
|
||||
Set this to y if you have an Ethernet network cards that uses the aQuantia
|
||||
AQC107/AQC108 chipset.
|
||||
|
||||
This option does not build any drivers; it casues the aQuantia
|
||||
This option does not build any drivers; it causes the aQuantia
|
||||
drivers that can be built to appear in the list of Ethernet drivers.
|
||||
|
||||
|
||||
|
@ -11,7 +11,7 @@ config NFC_ST_NCI_I2C
|
||||
select NFC_ST_NCI
|
||||
---help---
|
||||
This module adds support for an I2C interface to the
|
||||
STMicroelectronics NFC NCI chips familly.
|
||||
STMicroelectronics NFC NCI chips family.
|
||||
Select this if your platform is using the i2c bus.
|
||||
|
||||
If you choose to build a module, it'll be called st-nci_i2c.
|
||||
@ -23,7 +23,7 @@ config NFC_ST_NCI_SPI
|
||||
select NFC_ST_NCI
|
||||
---help---
|
||||
This module adds support for an SPI interface to the
|
||||
STMicroelectronics NFC NCI chips familly.
|
||||
STMicroelectronics NFC NCI chips family.
|
||||
Select this if your platform is using the spi bus.
|
||||
|
||||
If you choose to build a module, it'll be called st-nci_spi.
|
||||
|
@ -96,7 +96,7 @@ config NVDIMM_DAX
|
||||
help
|
||||
Support raw device dax access to a persistent memory
|
||||
namespace. For environments that want to hard partition
|
||||
peristent memory, this capability provides a mechanism to
|
||||
persistent memory, this capability provides a mechanism to
|
||||
sub-divide a namespace into character devices that can only be
|
||||
accessed via DAX (mmap(2)).
|
||||
|
||||
|
@ -774,7 +774,7 @@ config TOSHIBA_WMI
|
||||
WARNING: This driver is incomplete as it lacks a proper keymap and the
|
||||
*notify function only prints the ACPI event type value. Be warned that
|
||||
you will need to provide some information if you have a Toshiba model
|
||||
with WMI event hotkeys and want to help with the develpment of this
|
||||
with WMI event hotkeys and want to help with the development of this
|
||||
driver.
|
||||
|
||||
If you have a WMI-based hotkeys Toshiba laptop, say Y or M here.
|
||||
|
@ -182,7 +182,7 @@ config CHARGER_SBS
|
||||
tristate "SBS Compliant charger"
|
||||
depends on I2C
|
||||
help
|
||||
Say Y to include support for SBS compilant battery chargers.
|
||||
Say Y to include support for SBS compliant battery chargers.
|
||||
|
||||
config BATTERY_BQ27XXX
|
||||
tristate "BQ27xxx battery driver"
|
||||
|
@ -786,7 +786,7 @@ config SCSI_IBMVSCSIS
|
||||
depends on PPC_PSERIES && TARGET_CORE && SCSI && PCI
|
||||
help
|
||||
This is the IBM POWER Virtual SCSI Target Server
|
||||
This driver uses the SRP protocol for communication betwen servers
|
||||
This driver uses the SRP protocol for communication between servers
|
||||
guest and/or the host that run on the same server.
|
||||
More information on VSCSI protocol can be found at www.power.org
|
||||
|
||||
|
@ -21,6 +21,6 @@ config FANOTIFY_ACCESS_PERMISSIONS
|
||||
decisions concerning filesystem events. This is used by some fanotify
|
||||
listeners which need to scan files before allowing the system access to
|
||||
use those files. This is used by some anti-malware vendors and by some
|
||||
hierarchical storage managent systems.
|
||||
hierarchical storage management systems.
|
||||
|
||||
If unsure, say N.
|
||||
|
Loading…
Reference in New Issue
Block a user