All of lore.kernel.org
 help / color / mirror / Atom feed
From: Zhi Yong Wu <zwu.kernel@gmail.com>
To: linux-mm@kvack.org
Cc: linux-kernel@vger.kernel.org, akpm@linux-foundation.org,
	Zhi Yong Wu <wuzhy@linux.vnet.ibm.com>
Subject: [PATCH 3/3] mm, memory-failure: fix the typo in me_pagecache_dirty()
Date: Fri,  8 Nov 2013 20:47:38 +0800	[thread overview]
Message-ID: <1383914858-14533-3-git-send-email-zwu.kernel@gmail.com> (raw)
In-Reply-To: <1383914858-14533-1-git-send-email-zwu.kernel@gmail.com>

From: Zhi Yong Wu <wuzhy@linux.vnet.ibm.com>

Signed-off-by: Zhi Yong Wu <wuzhy@linux.vnet.ibm.com>
---
 mm/memory-failure.c |    2 +-
 1 files changed, 1 insertions(+), 1 deletions(-)

diff --git a/mm/memory-failure.c b/mm/memory-failure.c
index bf3351b..d8ec181 100644
--- a/mm/memory-failure.c
+++ b/mm/memory-failure.c
@@ -611,7 +611,7 @@ static int me_pagecache_clean(struct page *p, unsigned long pfn)
 }
 
 /*
- * Dirty cache page page
+ * Dirty cache page
  * Issues: when the error hit a hole page the error is not properly
  * propagated.
  */
-- 
1.7.6.5

--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org.  For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>

WARNING: multiple messages have this Message-ID (diff)
From: Zhi Yong Wu <zwu.kernel@gmail.com>
To: linux-mm@kvack.org
Cc: linux-kernel@vger.kernel.org, akpm@linux-foundation.org,
	Zhi Yong Wu <wuzhy@linux.vnet.ibm.com>
Subject: [PATCH 3/3] mm, memory-failure: fix the typo in me_pagecache_dirty()
Date: Fri,  8 Nov 2013 20:47:38 +0800	[thread overview]
Message-ID: <1383914858-14533-3-git-send-email-zwu.kernel@gmail.com> (raw)
In-Reply-To: <1383914858-14533-1-git-send-email-zwu.kernel@gmail.com>

From: Zhi Yong Wu <wuzhy@linux.vnet.ibm.com>

Signed-off-by: Zhi Yong Wu <wuzhy@linux.vnet.ibm.com>
---
 mm/memory-failure.c |    2 +-
 1 files changed, 1 insertions(+), 1 deletions(-)

diff --git a/mm/memory-failure.c b/mm/memory-failure.c
index bf3351b..d8ec181 100644
--- a/mm/memory-failure.c
+++ b/mm/memory-failure.c
@@ -611,7 +611,7 @@ static int me_pagecache_clean(struct page *p, unsigned long pfn)
 }
 
 /*
- * Dirty cache page page
+ * Dirty cache page
  * Issues: when the error hit a hole page the error is not properly
  * propagated.
  */
-- 
1.7.6.5


  parent reply	other threads:[~2013-11-08 12:47 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-11-08 12:47 [PATCH 1/3] mm, slub: fix the typo in include/linux/slub_def.h Zhi Yong Wu
2013-11-08 12:47 ` Zhi Yong Wu
2013-11-08 12:47 ` [PATCH 2/3] mm, slub: fix the typo in mm/slub.c Zhi Yong Wu
2013-11-08 12:47   ` Zhi Yong Wu
2013-11-08 16:21   ` Christoph Lameter
2013-11-08 16:21     ` Christoph Lameter
2013-11-08 12:47 ` Zhi Yong Wu [this message]
2013-11-08 12:47   ` [PATCH 3/3] mm, memory-failure: fix the typo in me_pagecache_dirty() Zhi Yong Wu
2013-11-08 16:21   ` Christoph Lameter
2013-11-08 16:21     ` Christoph Lameter
2013-11-22 22:59   ` Andrew Morton
2013-11-22 22:59     ` Andrew Morton
2013-11-08 16:21 ` [PATCH 1/3] mm, slub: fix the typo in include/linux/slub_def.h Christoph Lameter
2013-11-08 16:21   ` Christoph Lameter

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1383914858-14533-3-git-send-email-zwu.kernel@gmail.com \
    --to=zwu.kernel@gmail.com \
    --cc=akpm@linux-foundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=wuzhy@linux.vnet.ibm.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.