From: "tip-bot2 for Ricardo B. Marliere" <tip-bot2@linutronix.de>
To: linux-tip-commits@vger.kernel.org
Cc: "Greg Kroah-Hartman" <gregkh@linuxfoundation.org>,
"Ricardo B. Marliere" <ricardo@marliere.net>,
Thomas Gleixner <tglx@linutronix.de>,
x86@kernel.org, linux-kernel@vger.kernel.org
Subject: [tip: timers/core] clockevents: Make clockevents_subsys const
Date: Wed, 07 Feb 2024 14:20:18 -0000 [thread overview]
Message-ID: <170731561842.398.2305673935013890574.tip-bot2@tip-bot2> (raw)
In-Reply-To: <20240204-bus_cleanup-time-v1-2-207ec18e24b8@marliere.net>
The following commit has been merged into the timers/core branch of tip:
Commit-ID: 49f1ff50d49fb8b40bc0271177de8092226396e9
Gitweb: https://git.kernel.org/tip/49f1ff50d49fb8b40bc0271177de8092226396e9
Author: Ricardo B. Marliere <ricardo@marliere.net>
AuthorDate: Sun, 04 Feb 2024 10:40:16 -03:00
Committer: Thomas Gleixner <tglx@linutronix.de>
CommitterDate: Wed, 07 Feb 2024 15:11:24 +01:00
clockevents: Make clockevents_subsys const
Now that the driver core can properly handle constant struct bus_type,
move the clockevents_subsys variable to be a constant structure as well,
placing it into read-only memory which can not be modified at runtime.
Suggested-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Signed-off-by: Ricardo B. Marliere <ricardo@marliere.net>
Signed-off-by: Thomas Gleixner <tglx@linutronix.de>
Reviewed-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Link: https://lore.kernel.org/r/20240204-bus_cleanup-time-v1-2-207ec18e24b8@marliere.net
---
kernel/time/clockevents.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/kernel/time/clockevents.c b/kernel/time/clockevents.c
index 960143b..a7ca458 100644
--- a/kernel/time/clockevents.c
+++ b/kernel/time/clockevents.c
@@ -659,7 +659,7 @@ void tick_cleanup_dead_cpu(int cpu)
#endif
#ifdef CONFIG_SYSFS
-static struct bus_type clockevents_subsys = {
+static const struct bus_type clockevents_subsys = {
.name = "clockevents",
.dev_name = "clockevent",
};
next prev parent reply other threads:[~2024-02-07 14:20 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-04 13:40 [PATCH 0/2] time: struct bus_type cleanup Ricardo B. Marliere
2024-02-04 13:40 ` [PATCH 1/2] clocksource: make clocksource_subsys const Ricardo B. Marliere
2024-02-05 17:59 ` John Stultz
2024-02-07 14:20 ` [tip: timers/core] clocksource: Make " tip-bot2 for Ricardo B. Marliere
2024-02-04 13:40 ` [PATCH 2/2] clockevents: make clockevents_subsys const Ricardo B. Marliere
2024-02-07 14:20 ` tip-bot2 for Ricardo B. Marliere [this message]
2024-02-04 14:25 ` [PATCH 0/2] time: struct bus_type cleanup Greg Kroah-Hartman
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=170731561842.398.2305673935013890574.tip-bot2@tip-bot2 \
--to=tip-bot2@linutronix.de \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tip-commits@vger.kernel.org \
--cc=ricardo@marliere.net \
--cc=tglx@linutronix.de \
--cc=x86@kernel.org \
/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
all inboxes | Powered by JetHome®