diff options
| author | Matt LaPlante <kernel1@cyberdogtech.com> | 2006-10-03 16:53:09 -0400 |
|---|---|---|
| committer | Adrian Bunk <bunk@stusta.de> | 2006-10-03 16:53:09 -0400 |
| commit | 84eb8d0608af1576175307ed8fb3c8fde329e579 (patch) | |
| tree | 13f3223e6907ebe309328d460fe51ce7ac346ae1 /mm | |
| parent | 992caacf1141b31e94540eb31e0540e3da3a5e25 (diff) | |
Fix "can not" in Documentation and Kconfig
Randy brought it to my attention that in proper english "can not" should always
be written "cannot". I donot see any reason to argue, even if I mightnot
understand why this rule exists. This patch fixes "can not" in several
Documentation files as well as three Kconfigs.
Signed-off-by: Matt LaPlante <kernel1@cyberdogtech.com>
Acked-by: Randy Dunlap <rdunlap@xenotime.net>
Signed-off-by: Adrian Bunk <bunk@stusta.de>
Diffstat (limited to 'mm')
| -rw-r--r-- | mm/Kconfig | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/mm/Kconfig b/mm/Kconfig index f10fe51985a0..db7c55de92cd 100644 --- a/mm/Kconfig +++ b/mm/Kconfig | |||
| @@ -92,7 +92,7 @@ config HAVE_MEMORY_PRESENT | |||
| 92 | 92 | ||
| 93 | # | 93 | # |
| 94 | # SPARSEMEM_EXTREME (which is the default) does some bootmem | 94 | # SPARSEMEM_EXTREME (which is the default) does some bootmem |
| 95 | # allocations when memory_present() is called. If this can not | 95 | # allocations when memory_present() is called. If this cannot |
| 96 | # be done on your architecture, select this option. However, | 96 | # be done on your architecture, select this option. However, |
| 97 | # statically allocating the mem_section[] array can potentially | 97 | # statically allocating the mem_section[] array can potentially |
| 98 | # consume vast quantities of .bss, so be careful. | 98 | # consume vast quantities of .bss, so be careful. |