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

[mv-sheeva.git] / mm / msync.c

diff --git a/mm/msync.c b/mm/msync.c
index 2672b8dc3d894cad1b77016ecc8c78eab01eb714..bc6c95376366e394f6a21d98a985561184f2f46b 100644 (file)
--- a/mm/msync.c
+++ b/mm/msync.c
@@ -126,7 +126,7 @@ static unsigned long msync_page_range(struct vm_area_struct *vma,
  * write out the dirty pages and wait on the writeout and check the result.
  * Or the application may run fadvise(FADV_DONTNEED) against the fd to start
  * async writeout immediately.
- * So my _not_ starting I/O in MS_ASYNC we provide complete flexibility to
+ * So by _not_ starting I/O in MS_ASYNC we provide complete flexibility to
  * applications.
  */
 static int msync_interval(struct vm_area_struct *vma, unsigned long addr,