Mirrors_Framework/nuttx
1
0
Fork 0
mirror of https://github.com/apache/nuttx.git synced 2026-05-28 11:56:10 +08:00
Code Issues Actions 1 Packages Projects Releases Wiki Activity

style: fix spelling in code comments and strings

Browse Source
This commit is contained in:
Lars Kruse
2025-05-03 06:16:30 +02:00
committed by Xiang Xiao
parent b2315e98c4
commit 3ce85ca54e
1670 changed files with 3162 additions and 2991 deletions
Download Patch File Download Diff File Expand all files Collapse all files
fs/nxffs/Kconfig
+3 -3
View File
@@ -107,10 +107,10 @@ config NXFFS_TAILTHRESHOLD
Clean-up can either mean packing files together toward the end of
the file or, if files are deleted at the end of the file, clean up
can simply mean erasing the end of FLASH memory so that it can be
re-used again. However, doing this can also harm the life of the
reused again. However, doing this can also harm the life of the
FLASH part because it can mean that the tail end of the FLASH is
re-used too often. This threshold determines if/when it is worth
erased the tail end of FLASH and making it available for re-use
reused too often. This threshold determines if/when it is worth
erased the tail end of FLASH and making it available for reuse
(and possible over-wear). Default: 8192.
endif
fs/nxffs/nxffs_inode.c
+1 -1
View File
@@ -285,7 +285,7 @@ int nxffs_nextentry(FAR struct nxffs_volume_s *volume, off_t offset,
nerased = 0;
/* Check for the magic sequence indicating the start of an NXFFS
* inode. There is the possibility of this magic sequnce occurring
* inode. There is the possibility of this magic sequence occurring
* in FLASH data. However, the header CRC should distinguish
* between real NXFFS inode headers and such false alarms.
*/
fs/nxffs/nxffs_open.c
+1 -1
View File
@@ -605,7 +605,7 @@ static inline int nxffs_wropen(FAR struct nxffs_volume_s *volume,
}
/* Then just break out of the loop reporting success. Note
* that the alllocated inode name string is retained; it
* that the allocated inode name string is retained; it
* will be needed later to calculate the inode CRC.
*/
fs/nxffs/nxffs_pack.c
+1 -1
View File
@@ -785,7 +785,7 @@ static void nxffs_packtransfer(FAR struct nxffs_volume_s *volume,
uint16_t destlen = volume->geo.blocksize - pack->iooffset;
/* Dermined how much data is available in the src data block */
/* Determined how much data is available in the src data block */
uint16_t srclen = pack->src.blklen - pack->src.blkpos;
fs/nxffs/nxffs_read.c
+1 -1
View File
@@ -303,7 +303,7 @@ int nxffs_nextblock(FAR struct nxffs_volume_s *volume, off_t offset,
/* Check for the magic sequence indicating the start of an NXFFS
* data block or start of the next inode. There is the possibility
* of this magic sequnce occurring in FLASH data. However, the
* of this magic sequence occurring in FLASH data. However, the
* data block CRC should distinguish between real NXFFS data blocks
* headers and such false alarms.
*/