mirror of
https://github.com/apache/nuttx.git
synced 2026-06-04 23:03:27 +08:00
Fix lots of typos in C comments and Kconfig help text
This commit is contained in:
committed by
Gregory Nutt
parent
1783d344dc
commit
283b73edc5
+1
-1
@@ -46,7 +46,7 @@ config PSEUDOFS_SOFTLINKS
|
||||
default n
|
||||
depends on !DISABLE_PSEUDOFS_OPERATIONS
|
||||
---help---
|
||||
Enable support for soft links in the pseudeo file system. Soft
|
||||
Enable support for soft links in the pseudo file system. Soft
|
||||
links are not supported within mounted volumes by any NuttX file
|
||||
system. However, if this option is selected, then soft links
|
||||
may be add in the pseudo file system. This might be useful, for
|
||||
|
||||
+1
-1
@@ -21,7 +21,7 @@ config FS_RAMMAP
|
||||
into RAM. These copied files have some of the properties of
|
||||
standard memory mapped files.
|
||||
|
||||
See nuttx/fs/mmap/README.txt for additonal information.
|
||||
See nuttx/fs/mmap/README.txt for additional information.
|
||||
|
||||
if FS_RAMMAP
|
||||
endif
|
||||
|
||||
+1
-1
@@ -15,7 +15,7 @@ config NFS
|
||||
#if NFS
|
||||
|
||||
config NFS_STATISTICS
|
||||
bool "NFS Stastics"
|
||||
bool "NFS Statics"
|
||||
default n
|
||||
depends on NFS
|
||||
---help---
|
||||
|
||||
+1
-1
@@ -77,7 +77,7 @@ config NXFFS_PREALLOCATED
|
||||
---help---
|
||||
If CONFIG_NXFSS_PREALLOCATED is defined, then this is the single, pre-
|
||||
allocated NXFFS volume instance. Currently required because full,
|
||||
dynamic allocation of NXFFS volumes in not yet supporte.
|
||||
dynamic allocation of NXFFS volumes in not yet supported.
|
||||
|
||||
config NXFFS_ERASEDSTATE
|
||||
hex "FLASH erased state"
|
||||
|
||||
@@ -1151,7 +1151,7 @@ int procfs_register(FAR const struct procfs_entry_s *entry)
|
||||
* procfs entry table. If that table were actively in use, then that
|
||||
* could cause procfs logic to use a stale memory pointer! We avoid that
|
||||
* problem by requiring that the procfs file be unmounted when the new
|
||||
* entry is added. That requirment, however, is not enforced explicitly.
|
||||
* entry is added. That requirement, however, is not enforced explicitly.
|
||||
*
|
||||
* Locking the scheduler as done below is insufficient. As would be just
|
||||
* marking the entries as volatile.
|
||||
|
||||
Reference in New Issue
Block a user