aboutsummaryrefslogtreecommitdiffstats
path: root/Documentation/filesystems
diff options
context:
space:
mode:
Diffstat (limited to 'Documentation/filesystems')
-rw-r--r--Documentation/filesystems/hpfs.txt2
-rw-r--r--Documentation/filesystems/ntfs.txt2
-rw-r--r--Documentation/filesystems/relay.txt2
-rw-r--r--Documentation/filesystems/xip.txt2
4 files changed, 4 insertions, 4 deletions
diff --git a/Documentation/filesystems/hpfs.txt b/Documentation/filesystems/hpfs.txt
index 38aba03efc5e..fa45c3baed98 100644
--- a/Documentation/filesystems/hpfs.txt
+++ b/Documentation/filesystems/hpfs.txt
@@ -290,7 +290,7 @@ History
2902.07 More fixes for Warp Server. Now it really works 2902.07 More fixes for Warp Server. Now it really works
2912.08 Creating new files is not so slow on large disks 2912.08 Creating new files is not so slow on large disks
292 An attempt to sync deleted file does not generate filesystem error 292 An attempt to sync deleted file does not generate filesystem error
2932.09 Fixed error on extremly fragmented files 2932.09 Fixed error on extremely fragmented files
294 294
295 295
296 vim: set textwidth=80: 296 vim: set textwidth=80:
diff --git a/Documentation/filesystems/ntfs.txt b/Documentation/filesystems/ntfs.txt
index 81779068b09b..8ee10ec88293 100644
--- a/Documentation/filesystems/ntfs.txt
+++ b/Documentation/filesystems/ntfs.txt
@@ -349,7 +349,7 @@ end of the line.
349Note the "Should sync?" parameter "nosync" means that the two mirrors are 349Note the "Should sync?" parameter "nosync" means that the two mirrors are
350already in sync which will be the case on a clean shutdown of Windows. If the 350already in sync which will be the case on a clean shutdown of Windows. If the
351mirrors are not clean, you can specify the "sync" option instead of "nosync" 351mirrors are not clean, you can specify the "sync" option instead of "nosync"
352and the Device-Mapper driver will then copy the entirey of the "Source Device" 352and the Device-Mapper driver will then copy the entirety of the "Source Device"
353to the "Target Device" or if you specified multipled target devices to all of 353to the "Target Device" or if you specified multipled target devices to all of
354them. 354them.
355 355
diff --git a/Documentation/filesystems/relay.txt b/Documentation/filesystems/relay.txt
index 7fbb6ffe5769..18d23f9a18c7 100644
--- a/Documentation/filesystems/relay.txt
+++ b/Documentation/filesystems/relay.txt
@@ -351,7 +351,7 @@ If the current buffer is full, i.e. all sub-buffers remain unconsumed,
351the callback returns 0 to indicate that the buffer switch should not 351the callback returns 0 to indicate that the buffer switch should not
352occur yet, i.e. until the consumer has had a chance to read the 352occur yet, i.e. until the consumer has had a chance to read the
353current set of ready sub-buffers. For the relay_buf_full() function 353current set of ready sub-buffers. For the relay_buf_full() function
354to make sense, the consumer is reponsible for notifying the relay 354to make sense, the consumer is responsible for notifying the relay
355interface when sub-buffers have been consumed via 355interface when sub-buffers have been consumed via
356relay_subbufs_consumed(). Any subsequent attempts to write into the 356relay_subbufs_consumed(). Any subsequent attempts to write into the
357buffer will again invoke the subbuf_start() callback with the same 357buffer will again invoke the subbuf_start() callback with the same
diff --git a/Documentation/filesystems/xip.txt b/Documentation/filesystems/xip.txt
index 6c0cef10eb4d..3cc4010521a0 100644
--- a/Documentation/filesystems/xip.txt
+++ b/Documentation/filesystems/xip.txt
@@ -19,7 +19,7 @@ completely. With execute-in-place, read&write type operations are performed
19directly from/to the memory backed storage device. For file mappings, the 19directly from/to the memory backed storage device. For file mappings, the
20storage device itself is mapped directly into userspace. 20storage device itself is mapped directly into userspace.
21 21
22This implementation was initialy written for shared memory segments between 22This implementation was initially written for shared memory segments between
23different virtual machines on s390 hardware to allow multiple machines to 23different virtual machines on s390 hardware to allow multiple machines to
24share the same binaries and libraries. 24share the same binaries and libraries.
25 25