[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20230313053929.84607-1-wangkefeng.wang@huawei.com>
Date: Mon, 13 Mar 2023 13:39:29 +0800
From: Kefeng Wang <wangkefeng.wang@...wei.com>
To: Naoya Horiguchi <naoya.horiguchi@....com>,
Andrew Morton <akpm@...ux-foundation.org>, <linux-mm@...ck.org>
CC: Miaohe Lin <linmiaohe@...wei.com>, <linux-kernel@...r.kernel.org>,
Kefeng Wang <wangkefeng.wang@...wei.com>,
David Hildenbrand <david@...hat.com>
Subject: [PATCH v2] mm: memory-failure: directly use IS_ENABLED(CONFIG_HWPOISON_INJECT)
It's more clear and simple to just use IS_ENABLED(CONFIG_HWPOISON_INJECT)
to check whether or not to enable HWPoison injector module instead of
CONFIG_HWPOISON_INJECT/CONFIG_HWPOISON_INJECT_MODULE.
Reviewed-by: David Hildenbrand <david@...hat.com>
Acked-by: Naoya Horiguchi <naoya.horiguchi@....com>
Signed-off-by: Kefeng Wang <wangkefeng.wang@...wei.com>
---
v2:
- add Ack/Rb, also update the suject/changelog suggested by Andrew
mm/memory-failure.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/mm/memory-failure.c b/mm/memory-failure.c
index fae9baf3be16..f761704d27d7 100644
--- a/mm/memory-failure.c
+++ b/mm/memory-failure.c
@@ -168,7 +168,7 @@ static bool page_handle_poison(struct page *page, bool hugepage_or_freepage, boo
return true;
}
-#if defined(CONFIG_HWPOISON_INJECT) || defined(CONFIG_HWPOISON_INJECT_MODULE)
+#if IS_ENABLED(CONFIG_HWPOISON_INJECT)
u32 hwpoison_filter_enable = 0;
u32 hwpoison_filter_dev_major = ~0U;
--
2.35.3
Powered by blists - more mailing lists