From 16538c40776b8be6b0f23966e08fdc7b8fff823f Mon Sep 17 00:00:00 2001
From: Amos Waterland <apw@us.ibm.com>
Date: Fri, 24 Mar 2006 18:30:53 +0100
Subject: [PATCH] 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>
---
 mm/msync.c | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/mm/msync.c b/mm/msync.c
index 2672b8dc3d894..bc6c95376366e 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,
-- 
GitLab