From: Igor Putko <igorpetindev@gmail.com>
To: tj@kernel.org, jiangshanlai@gmail.com, peterz@infradead.org,
sshegde@linux.ibm.com, vschneid@redhat.com, pauld@redhat.com
Cc: linux-kernel@vger.kernel.org, Igor Putko <igorpetindev@gmail.com>
Subject: [PATCH 2/2] kernel/stop_machine: remove redundant initialization for stop_machine_initialized
Date: Tue, 23 Jun 2026 15:01:01 +0300 [thread overview]
Message-ID: <20260623120101.4942-3-igorpetindev@gmail.com> (raw)
In-Reply-To: <20260623120101.4942-1-igorpetindev@gmail.com>
The static variable 'stop_machine_initialized' is implicitly initialized
to false. Remove the explicit initialization to follow the Linux
kernel coding style.
Signed-off-by: Igor Putko <igorpetindev@gmail.com>
---
kernel/stop_machine.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/kernel/stop_machine.c b/kernel/stop_machine.c
index 773d8e9ae30c..96dfdaf93c06 100644
--- a/kernel/stop_machine.c
+++ b/kernel/stop_machine.c
@@ -47,7 +47,7 @@ struct cpu_stopper {
};
static DEFINE_PER_CPU(struct cpu_stopper, cpu_stopper);
-static bool stop_machine_initialized = false;
+static bool stop_machine_initialized;
void print_stop_info(const char *log_lvl, struct task_struct *task)
{
--
2.34.1
next prev parent reply other threads:[~2026-06-23 12:01 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-23 12:00 [PATCH 0/2] kernel: remove redundant static variable initializations Igor Putko
2026-06-23 12:01 ` [PATCH 1/2] kernel/workqueue: remove redundant initialization for static variables Igor Putko
2026-06-23 12:01 ` Igor Putko [this message]
2026-06-23 12:32 ` [PATCH 2/2] kernel/stop_machine: remove redundant initialization for stop_machine_initialized Peter Zijlstra
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=20260623120101.4942-3-igorpetindev@gmail.com \
--to=igorpetindev@gmail.com \
--cc=jiangshanlai@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=pauld@redhat.com \
--cc=peterz@infradead.org \
--cc=sshegde@linux.ibm.com \
--cc=tj@kernel.org \
--cc=vschneid@redhat.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.