Commit 16538c40776b8be6b0f23966e08fdc7b8fff823f

Authored by Amos Waterland
Committed by Adrian Bunk
1 parent de0dfcdf55

The comment describing how MS_ASYNC works in msync.c is confusing

because of a typo.  This patch just changes "my" to "by", which I
believe was the original intent.

Signed-off-by: Adrian Bunk <bunk@stusta.de>

Showing 1 changed file with 1 additions and 1 deletions Side-by-side Diff

... ... @@ -126,7 +126,7 @@
126 126 * write out the dirty pages and wait on the writeout and check the result.
127 127 * Or the application may run fadvise(FADV_DONTNEED) against the fd to start
128 128 * async writeout immediately.
129   - * So my _not_ starting I/O in MS_ASYNC we provide complete flexibility to
  129 + * So by _not_ starting I/O in MS_ASYNC we provide complete flexibility to
130 130 * applications.
131 131 */
132 132 static int msync_interval(struct vm_area_struct *vma, unsigned long addr,