Trivial fixes. Cc: Randy Dunlap <rdunlap@xxxxxxxxxxxxx> Signed-off-by: Fabian Frederick <fabf@xxxxxxxxx> --- Documentation/filesystems/qnx6.txt | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/Documentation/filesystems/qnx6.txt b/Documentation/filesystems/qnx6.txt index 4086797..79bf2d0 100644 --- a/Documentation/filesystems/qnx6.txt +++ b/Documentation/filesystems/qnx6.txt @@ -16,7 +16,7 @@ qnx6fs shares many properties with traditional Unix filesystems. It has the concepts of blocks, inodes and directories. On QNX it is possible to create little endian and big endian qnx6 filesystems. This feature makes it possible to create and use a different endianness fs -for the target (QNX is used on quite a range of embedded systems) plattform +for the target (QNX is used on quite a range of embedded systems) platform running on a different endianness. The Linux driver handles endianness transparently. (LE and BE) @@ -98,7 +98,7 @@ It is a specially formatted file containing records which associate each name with an inode number. '.' inode number points to the directory inode '..' inode number points to the parent directory inode -Eeach filename record additionally got a filename length field. +Each filename record additionally got a filename length field. One special case are long filenames or subdirectory names. These got set a filename length field of 0xff in the corresponding directory @@ -163,7 +163,7 @@ tree structures are treated as system blocks. The rational behind that is that a write request can work on a new snapshot (system area of the inactive - resp. lower serial numbered superblock) while -at the same time there is still a complete stable filesystem structer in the +at the same time there is still a complete stable filesystem structure in the other half of the system area. When finished with writing (a sync write is completed, the maximum sync leap -- 1.8.4.5 -- To unsubscribe from this list: send the line "unsubscribe linux-doc" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
