Replace 'the the' with 'the'

This commit is contained in:
Gregory Nutt
2017-05-11 13:15:13 -06:00
parent 0f7210b0ae
commit 41680d376d
6 changed files with 15 additions and 16 deletions
+8 -9
View File
@@ -352,8 +352,8 @@ static int _inode_search(FAR struct inode_search_s *desc)
status = _inode_linktarget(node, desc); status = _inode_linktarget(node, desc);
if (status < 0) if (status < 0)
{ {
/* Probably means that the the target of the symbolic /* Probably means that the target of the symbolic link
* link does not exist. * does not exist.
*/ */
ret = status; ret = status;
@@ -366,8 +366,8 @@ static int _inode_search(FAR struct inode_search_s *desc)
if (newnode != node) if (newnode != node)
{ {
/* The node was a valid symbolic link and we have /* The node was a valid symbolic link and we have
* jumped to a different, spot in the the pseudo * jumped to a different, spot in the pseudo file
* file system tree. * system tree.
*/ */
/* Check if this took us to a mountpoint. */ /* Check if this took us to a mountpoint. */
@@ -539,11 +539,10 @@ int inode_search(FAR struct inode_search_s *desc)
/* There would be no problem in this case if the link was to /* There would be no problem in this case if the link was to
* either to the root directory of the MOUNTPOINT or to a * either to the root directory of the MOUNTPOINT or to a
* regular file within the the mounted volume. However, * regular file within the mounted volume. However, there
* there is a problem if the symbolic link is to a directory * is a problem if the symbolic link is to a directory within
* within the mounted volume. In that case, the 'relpath' * the mounted volume. In that case, the 'relpath' will be
* will be relative to the symbolic link and not to the * relative to the symbolic link and not to the MOUNTPOINT.
* MOUNTPOINT.
* *
* We will handle the worst case by creating the full path * We will handle the worst case by creating the full path
* excluding the symbolic link and performing the look-up * excluding the symbolic link and performing the look-up
+1 -1
View File
@@ -22,7 +22,7 @@ config FS_TMPFS_BLOCKSIZE
of blocks. There are, of course, no blocks with the TMPFS. This of blocks. There are, of course, no blocks with the TMPFS. This
options is available to control how sizes are reported. For very options is available to control how sizes are reported. For very
small TMPFS systems, you might want to set this to something smaller small TMPFS systems, you might want to set this to something smaller
the the usual 512 bytes. the usual 512 bytes.
config FS_TMPFS_DIRECTORY_ALLOCGUARD config FS_TMPFS_DIRECTORY_ALLOCGUARD
int "Directory object over-allocation" int "Directory object over-allocation"
+2 -2
View File
@@ -962,7 +962,7 @@ static int tmpfs_find_object(FAR struct tmpfs_s *fs,
next_segment = strtok_r(NULL, "/", &tkptr); next_segment = strtok_r(NULL, "/", &tkptr);
/* Search the the next directory. */ /* Search the next directory. */
tdo = next_tdo; tdo = next_tdo;
@@ -1301,7 +1301,7 @@ static int tmpfs_foreach(FAR struct tmpfs_directory_s *tdo,
FAR struct tmpfs_directory_s *next = FAR struct tmpfs_directory_s *next =
(FAR struct tmpfs_directory_s *)to; (FAR struct tmpfs_directory_s *)to;
/* Yes.. traverse its children first in the case the the final /* Yes.. traverse its children first in the case the final
* action will be to delete the directory. * action will be to delete the directory.
*/ */
+1 -1
View File
@@ -37,7 +37,7 @@ fs/unionfs/README.txt
in functions provide CGI programs. But the BINFS file system cannot hold in functions provide CGI programs. But the BINFS file system cannot hold
content. Fixed content would need to be retained in a more standard file content. Fixed content would need to be retained in a more standard file
system such as ROMFS. With this Union File System, you can overly the system such as ROMFS. With this Union File System, you can overly the
BINFS mountpoint on the the ROMFS mountpoint, providing a single directory BINFS mountpoint on the ROMFS mountpoint, providing a single directory
that appears to contain the executables from the BINFS file system along that appears to contain the executables from the BINFS file system along
with the web content from the ROMFS file system. with the web content from the ROMFS file system.
+2 -2
View File
@@ -275,7 +275,7 @@ static FAR const char *unionfs_offsetpath(FAR const char *relpath,
FAR const char *trypath; FAR const char *trypath;
int pfxlen; int pfxlen;
/* Is there a prefix on the the path to this file system? */ /* Is there a prefix on the path to this file system? */
if (prefix && (pfxlen = strlen(prefix)) > 0) if (prefix && (pfxlen = strlen(prefix)) > 0)
{ {
@@ -1634,7 +1634,7 @@ static int unionfs_readdir(struct inode *mountpt, struct fs_dirent_s *dir)
DEBUGASSERT(dir); DEBUGASSERT(dir);
fu = &dir->u.unionfs; fu = &dir->u.unionfs;
/* Check if we are at the end of the the directory listing. */ /* Check if we are at the end of the directory listing. */
if (fu->fu_eod) if (fu->fu_eod)
{ {
+1 -1
View File
@@ -82,7 +82,7 @@
* *
* Returned Value: * Returned Value:
* On success, zero (OK) is returned. Otherwise, -1 (ERROR) is returned * On success, zero (OK) is returned. Otherwise, -1 (ERROR) is returned
* the the errno variable is set appropriately. * the errno variable is set appropriately.
* *
****************************************************************************/ ****************************************************************************/