From: Andi Kleen <andi@firstfloor.org>
To: Wanpeng Li <liwanp@linux.vnet.ibm.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Andi Kleen <andi@firstfloor.org>,
Fengguang Wu <fengguang.wu@intel.com>,
Naoya Horiguchi <n-horiguchi@ah.jp.nec.com>,
Tony Luck <tony.luck@intel.com>,
gong.chen@linux.intel.com, linux-mm@kvack.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v4 1/10] mm/hwpoison: fix lose PG_dirty flag for errors on mlocked pages
Date: Thu, 29 Aug 2013 08:00:15 +0200 [thread overview]
Message-ID: <20130829060015.GK19750@two.firstfloor.org> (raw)
In-Reply-To: <1377506774-5377-1-git-send-email-liwanp@linux.vnet.ibm.com>
I did a quick read and the patches look all good to me
(except the one just moving code around -- seems pointless,
forward declarations are totally fine)
Acked-by: Andi Kleen <ak@linux.intel.com>
-Andi
--
ak@linux.intel.com -- Speaking for myself only.
--
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>
next prev parent reply other threads:[~2013-08-29 6:00 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-26 8:46 Wanpeng Li
2013-08-26 8:46 ` [PATCH v4 2/10] mm/hwpoison: don't need to hold compound lock for hugetlbfs page Wanpeng Li
2013-08-26 8:46 ` [PATCH v4 3/10] mm/hwpoison: fix race against poison thp Wanpeng Li
2013-08-26 8:46 ` [PATCH v4 4/10] mm/hwpoison: replacing atomic_long_sub() with atomic_long_dec() Wanpeng Li
2013-08-26 8:46 ` [PATCH v4 5/10] mm/hwpoison: don't set migration type twice to avoid hold heavy contend zone->lock Wanpeng Li
2013-08-26 8:46 ` [PATCH v4 6/10] mm/hwpoison: drop forward reference declarations __soft_offline_page() Wanpeng Li
2013-08-26 8:46 ` [PATCH v4 7/10] mm/hwpoison: add '#' to madvise_hwpoison Wanpeng Li
2013-08-26 8:46 ` [PATCH v4 8/10] mm/hwpoison: fix memory failure still hold reference count after unpoison empty zero page Wanpeng Li
2013-08-26 15:45 ` Naoya Horiguchi
2013-08-26 23:26 ` Wanpeng Li
2013-08-26 23:26 ` Wanpeng Li
2013-08-27 0:12 ` Naoya Horiguchi
2013-08-27 0:21 ` Wanpeng Li
2013-08-27 0:21 ` Wanpeng Li
[not found] ` <521bf0fc.4950320a.76ab.0f2dSMTPIN_ADDED_BROKEN@mx.google.com>
2013-08-27 0:46 ` Naoya Horiguchi
2013-08-27 1:17 ` Wanpeng Li
2013-08-27 1:17 ` Wanpeng Li
[not found] ` <521bfe37.83892b0a.1b94.2e7cSMTPIN_ADDED_BROKEN@mx.google.com>
2013-08-27 1:34 ` Naoya Horiguchi
2013-08-27 1:48 ` Wanpeng Li
2013-08-27 1:48 ` Wanpeng Li
[not found] ` <521be416.a5e8420a.6786.09d1SMTPIN_ADDED_BROKEN@mx.google.com>
2013-08-26 23:31 ` Andrew Morton
2013-08-26 23:40 ` Wanpeng Li
2013-08-26 23:40 ` Wanpeng Li
2013-08-26 8:46 ` [PATCH v4 9/10] mm/hwpoison: change permission of corrupt-pfn/unpoison-pfn to 0400 Wanpeng Li
2013-08-26 9:08 ` Wanpeng Li
2013-08-26 9:08 ` Wanpeng Li
2013-08-26 15:47 ` Naoya Horiguchi
2013-08-26 8:46 ` [PATCH v4 10/10] mm/hwpoison: fix bug triggered by unpoison empty zero page Wanpeng Li
2013-08-29 6:00 ` Andi Kleen [this message]
2013-08-29 6:17 ` [PATCH v4 1/10] mm/hwpoison: fix lose PG_dirty flag for errors on mlocked pages Wanpeng Li
2013-08-29 6:17 ` Wanpeng Li
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=20130829060015.GK19750@two.firstfloor.org \
--to=andi@firstfloor.org \
--cc=akpm@linux-foundation.org \
--cc=fengguang.wu@intel.com \
--cc=gong.chen@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=liwanp@linux.vnet.ibm.com \
--cc=n-horiguchi@ah.jp.nec.com \
--cc=tony.luck@intel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox