Commit 6b2aac42b20f495d9ea220036f57596d525d4233
Committed by
Jiri Kosina
1 parent
b40b26ccfc
Exists in
smarc-l5.0.0_1.0.0-ga
and in
5 other branches
Fix typo in various Kconfig file
Correct spelling typo in various Kconfig file. Signed-off-by: Masanari Iida <standby24x7@gmail.com> Signed-off-by: Jiri Kosina <jkosina@suse.cz>
Showing 15 changed files with 19 additions and 19 deletions Side-by-side Diff
- arch/m68k/Kconfig.cpu
- arch/mips/Kconfig
- arch/mips/Kconfig.debug
- arch/openrisc/Kconfig
- arch/powerpc/platforms/Kconfig.cputype
- arch/powerpc/platforms/pseries/Kconfig
- arch/sh/Kconfig.cpu
- drivers/devfreq/Kconfig
- drivers/hid/Kconfig
- drivers/hwmon/Kconfig
- drivers/i2c/busses/Kconfig
- drivers/mfd/Kconfig
- drivers/ptp/Kconfig
- drivers/watchdog/Kconfig
- drivers/xen/Kconfig
arch/m68k/Kconfig.cpu
... | ... | @@ -7,7 +7,7 @@ |
7 | 7 | help |
8 | 8 | The Freescale (was Motorola) M68K family of processors implements |
9 | 9 | the full 68000 processor instruction set. |
10 | - The Freescale ColdFire family of processors is a modern derivitive | |
10 | + The Freescale ColdFire family of processors is a modern derivative | |
11 | 11 | of the 68000 processor family. They are mainly targeted at embedded |
12 | 12 | applications, and are all System-On-Chip (SOC) devices, as opposed |
13 | 13 | to stand alone CPUs. They implement a subset of the original 68000 |
arch/mips/Kconfig
... | ... | @@ -1001,12 +1001,12 @@ |
1001 | 1001 | bool |
1002 | 1002 | |
1003 | 1003 | # |
1004 | -# Endianess selection. Sufficiently obscure so many users don't know what to | |
1004 | +# Endianness selection. Sufficiently obscure so many users don't know what to | |
1005 | 1005 | # answer,so we try hard to limit the available choices. Also the use of a |
1006 | 1006 | # choice statement should be more obvious to the user. |
1007 | 1007 | # |
1008 | 1008 | choice |
1009 | - prompt "Endianess selection" | |
1009 | + prompt "Endianness selection" | |
1010 | 1010 | help |
1011 | 1011 | Some MIPS machines can be configured for either little or big endian |
1012 | 1012 | byte order. These modes require different kernels and a different |
arch/mips/Kconfig.debug
arch/openrisc/Kconfig
... | ... | @@ -141,7 +141,7 @@ |
141 | 141 | bool "Check for kernel stack overflow" |
142 | 142 | default y |
143 | 143 | help |
144 | - Make extra checks for space avaliable on stack in some | |
144 | + Make extra checks for space available on stack in some | |
145 | 145 | critical functions. This will cause kernel to run a bit slower, |
146 | 146 | but will catch most of kernel stack overruns and exit gracefuly. |
147 | 147 |
arch/powerpc/platforms/Kconfig.cputype
... | ... | @@ -258,7 +258,7 @@ |
258 | 258 | default y |
259 | 259 | ---help--- |
260 | 260 | The PID register in server is used explicitly for ICSWX. In |
261 | - embedded systems PID managment is done by the system. | |
261 | + embedded systems PID management is done by the system. | |
262 | 262 | |
263 | 263 | config PPC_ICSWX_USE_SIGILL |
264 | 264 | bool "Should a bad CT cause a SIGILL?" |
... | ... | @@ -266,7 +266,7 @@ |
266 | 266 | default n |
267 | 267 | ---help--- |
268 | 268 | Should a bad CT used for "non-record form ICSWX" cause an |
269 | - illegal intruction signal or should it be silent as | |
269 | + illegal instruction signal or should it be silent as | |
270 | 270 | architected. |
271 | 271 | |
272 | 272 | If in doubt, say N here. |
arch/powerpc/platforms/pseries/Kconfig
... | ... | @@ -67,7 +67,7 @@ |
67 | 67 | |
68 | 68 | This option will only enable the IO event platform code. You |
69 | 69 | will still need to enable or compile the actual drivers |
70 | - that use this infrastruture to handle IO event interrupts. | |
70 | + that use this infrastructure to handle IO event interrupts. | |
71 | 71 | |
72 | 72 | Say Y if you are unsure. |
73 | 73 |
arch/sh/Kconfig.cpu
drivers/devfreq/Kconfig
... | ... | @@ -16,7 +16,7 @@ |
16 | 16 | is attached to a single device and returns a "representative" |
17 | 17 | clock frequency of the device, which is also attached |
18 | 18 | to a device by 1-to-1. The device registering devfreq takes the |
19 | - responsiblity to "interpret" the representative frequency and | |
19 | + responsibility to "interpret" the representative frequency and | |
20 | 20 | to set its every clock accordingly with the "target" callback |
21 | 21 | given to devfreq. |
22 | 22 |
drivers/hid/Kconfig
drivers/hwmon/Kconfig
... | ... | @@ -318,7 +318,7 @@ |
318 | 318 | tristate "Temperature sensor on Samsung EXYNOS4" |
319 | 319 | depends on ARCH_EXYNOS4 |
320 | 320 | help |
321 | - If you say yes here you get support for TMU (Thermal Managment | |
321 | + If you say yes here you get support for TMU (Thermal Management | |
322 | 322 | Unit) on SAMSUNG EXYNOS4 series of SoC. |
323 | 323 | |
324 | 324 | This driver can also be built as a module. If so, the module |
drivers/i2c/busses/Kconfig
... | ... | @@ -351,7 +351,7 @@ |
351 | 351 | For details please see http://www.ti.com/davinci |
352 | 352 | |
353 | 353 | config I2C_DESIGNWARE_PLATFORM |
354 | - tristate "Synopsys DesignWare Platfrom" | |
354 | + tristate "Synopsys DesignWare Platform" | |
355 | 355 | depends on HAVE_CLK |
356 | 356 | help |
357 | 357 | If you say yes to this option, support will be included for the |
drivers/mfd/Kconfig
... | ... | @@ -407,7 +407,7 @@ |
407 | 407 | select MFD_CORE |
408 | 408 | help |
409 | 409 | Say yes here to support for Maxim Semiconductor MAX8925. This is |
410 | - a Power Management IC. This driver provies common support for | |
410 | + a Power Management IC. This driver provides common support for | |
411 | 411 | accessing the device, additional drivers must be enabled in order |
412 | 412 | to use the functionality of the device. |
413 | 413 | |
... | ... | @@ -430,7 +430,7 @@ |
430 | 430 | help |
431 | 431 | Say yes here to support for Maxim Semiconductor MAX8998 and |
432 | 432 | National Semiconductor LP3974. This is a Power Management IC. |
433 | - This driver provies common support for accessing the device, | |
433 | + This driver provides common support for accessing the device, | |
434 | 434 | additional drivers must be enabled in order to use the functionality |
435 | 435 | of the device. |
436 | 436 | |
... | ... | @@ -441,7 +441,7 @@ |
441 | 441 | select REGMAP_I2C |
442 | 442 | help |
443 | 443 | Support for the Samsung Electronics S5M MFD series. |
444 | - This driver provies common support for accessing the device, | |
444 | + This driver provides common support for accessing the device, | |
445 | 445 | additional drivers must be enabled in order to use the functionality |
446 | 446 | of the device |
447 | 447 |
drivers/ptp/Kconfig
... | ... | @@ -70,7 +70,7 @@ |
70 | 70 | using the SO_TIMESTAMPING API. |
71 | 71 | |
72 | 72 | In order for this to work, your MAC driver must also |
73 | - implement the skb_tx_timetamp() function. | |
73 | + implement the skb_tx_timestamp() function. | |
74 | 74 | |
75 | 75 | config PTP_1588_CLOCK_PCH |
76 | 76 | tristate "Intel PCH EG20T as PTP clock" |
drivers/watchdog/Kconfig
... | ... | @@ -937,7 +937,7 @@ |
937 | 937 | tristate "Broadcom BCM47xx Watchdog Timer" |
938 | 938 | depends on BCM47XX |
939 | 939 | help |
940 | - Hardware driver for the Broadcom BCM47xx Watchog Timer. | |
940 | + Hardware driver for the Broadcom BCM47xx Watchdog Timer. | |
941 | 941 | |
942 | 942 | config RC32434_WDT |
943 | 943 | tristate "IDT RC32434 SoC Watchdog Timer" |
drivers/xen/Kconfig
... | ... | @@ -71,7 +71,7 @@ |
71 | 71 | tristate "Xen /dev/xen/evtchn device" |
72 | 72 | default y |
73 | 73 | help |
74 | - The evtchn driver allows a userspace process to triger event | |
74 | + The evtchn driver allows a userspace process to trigger event | |
75 | 75 | channels and to receive notification of an event channel |
76 | 76 | firing. |
77 | 77 | If in doubt, say yes. |