From: Amos Waterland <apw@us.ibm.com>
Date: Fri, 24 Mar 2006 17:30:53 +0000 (+0100)
Subject: The comment describing how MS_ASYNC works in msync.c is confusing
X-Git-Url: http://drtracing.org/?a=commitdiff_plain;h=16538c40776b8be6b0f23966e08fdc7b8fff823f;p=deliverable%2Flinux.git

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>
---

diff --git a/mm/msync.c b/mm/msync.c
index 2672b8dc3d89..bc6c95376366 100644
--- 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,