[FS]:Fixed spacing and typo issues in code comment descriptions

[Desc]:as title

Signed-off-by: pengyinjie <pengyinjie@xiaomi.com>
This commit is contained in:
pengyinjie 2024-06-19 16:51:56 +08:00 committed by Xiang Xiao
parent 572daf46c2
commit cbc9b98075
2 changed files with 9 additions and 9 deletions

View File

@ -202,7 +202,7 @@ int file_mmap(FAR struct file *filep, FAR void *start, size_t length,
* only file system that meets this requirement.
* b. The underlying block driver supports the BIOC_XIPBASE ioctl
* command that maps the underlying media to a randomly accessible
* address. At present, only the RAM/ROM disk driver does this.
* address. At present, only the RAM/ROM disk driver does this.
*
* 2. If CONFIG_FS_RAMMAP is defined in the configuration, then mmap() will
* support simulation of memory mapped files by copying files whole

View File

@ -118,19 +118,19 @@ int file_munmap(FAR void *start, size_t length)
* 1. mmap() is the API that is used to support direct access to random
* access media under the following very restrictive conditions:
*
* a. The filesystem impelements the mmap file operation. Any file
* a. The filesystem implements the mmap file operation. Any file
* system that maps files contiguously on the media should support
* this ioctl. (vs. file system that scatter files over the media
* in non-contiguous sectors). As of this writing, ROMFS is the
* only file system that meets this requirement.
* b. The underlying block driver supports the BIOC_XIPBASE ioctl
* command that maps the underlying media to a randomly accessible
* address. At present, only the RAM/ROM disk driver does this.
* address. At present, only the RAM/ROM disk driver does this.
*
* munmap() is still not required in this first case. In this first
* The mapped address is a static address in the MCUs address space
* does not need to be munmapped. Support for munmap() in this case
* provided by the simple definition in sys/mman.h:
* munmap() is still not required in this first case. The mapped address
* is a static address in the MCUs address space does not need to be
* munmapped. Support for munmap() in this case provided by the simple
* definition in sys/mman.h:
*
* #define munmap(start, length)
*
@ -141,10 +141,10 @@ int file_munmap(FAR void *start, size_t length)
*
* Input Parameters:
* start The start address of the mapping to delete. For this
* simplified munmap() implementation, the *must* be the start
* simplified munmap() implementation, the must be the start
* address of the memory region (the same address returned by
* mmap()).
* length The length region to be umapped.
* length The length region to be unmapped.
*
* Returned Value:
* On success, munmap() returns 0, on failure -1, and errno is set