From: Igor Putko <igorpetindev@gmail.com>
To: ryabinin.a.a@gmail.com, glider@google.com, andreyknvl@gmail.com,
dvyukov@google.com, vincenzo.frascino@arm.com,
linmiaohe@huawei.com, nao.horiguchi@gmail.com
Cc: akpm@linux-foundation.org, kasan-dev@googlegroups.com,
linux-mm@kvack.org, linux-kernel@vger.kernel.org,
Igor Putko <igorpetindev@gmail.com>
Subject: [PATCH 2/2] mm/memory-failure: remove redundant initialization for hw_memory_failure
Date: Tue, 23 Jun 2026 14:47:43 +0300 [thread overview]
Message-ID: <20260623114743.4565-3-igorpetindev@gmail.com> (raw)
In-Reply-To: <20260623114743.4565-1-igorpetindev@gmail.com>
The static variable 'hw_memory_failure' is implicitly initialized
to false. Remove the explicit initialization to follow the Linux
kernel coding style.
Signed-off-by: Igor Putko <igorpetindev@gmail.com>
---
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 51508a55c405..4963ea9f6ec6 100644
--- a/mm/memory-failure.c
+++ b/mm/memory-failure.c
@@ -76,7 +76,7 @@ static int sysctl_enable_soft_offline __read_mostly = 1;
atomic_long_t num_poisoned_pages __read_mostly = ATOMIC_LONG_INIT(0);
-static bool hw_memory_failure __read_mostly = false;
+static bool hw_memory_failure __read_mostly;
static DEFINE_MUTEX(mf_mutex);
--
2.34.1
prev parent reply other threads:[~2026-06-23 11:47 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-23 11:47 [PATCH 0/2] mm: remove redundant static variable initializations Igor Putko
2026-06-23 11:47 ` [PATCH 1/2] mm/kasan: remove redundant initialization for kasan_flag_write_only Igor Putko
2026-06-23 11:47 ` Igor Putko [this message]
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=20260623114743.4565-3-igorpetindev@gmail.com \
--to=igorpetindev@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=andreyknvl@gmail.com \
--cc=dvyukov@google.com \
--cc=glider@google.com \
--cc=kasan-dev@googlegroups.com \
--cc=linmiaohe@huawei.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=nao.horiguchi@gmail.com \
--cc=ryabinin.a.a@gmail.com \
--cc=vincenzo.frascino@arm.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