From: tip-bot for Ben Dooks <tipbot@zytor.com>
To: linux-tip-commits@vger.kernel.org
Cc: linux-kernel@vger.kernel.org, hpa@zytor.com, mingo@kernel.org,
tglx@linutronix.de, ben.dooks@codethink.co.uk
Subject: [tip:timers/core] clockevents: Make clockevents_subsys static
Date: Tue, 19 Jul 2016 01:51:42 -0700 [thread overview]
Message-ID: <tip-775be506266a860f141f6b848c92c316c602a94f@git.kernel.org> (raw)
In-Reply-To: <1466178974-7105-1-git-send-email-ben.dooks@codethink.co.uk>
Commit-ID: 775be506266a860f141f6b848c92c316c602a94f
Gitweb: http://git.kernel.org/tip/775be506266a860f141f6b848c92c316c602a94f
Author: Ben Dooks <ben.dooks@codethink.co.uk>
AuthorDate: Fri, 17 Jun 2016 16:56:14 +0100
Committer: Thomas Gleixner <tglx@linutronix.de>
CommitDate: Tue, 19 Jul 2016 10:48:06 +0200
clockevents: Make clockevents_subsys static
The clockevents_subsys struct is used for sysfs support and
is not declared or used outside the file it is defined in.
Fix the following warning by making it static:
kernel/time/clockevents.c:648:17: warning: symbol 'clockevents_subsys' was not declared. Should it be static?
Signed-off-by: Ben Dooks <ben.dooks@codethink.co.uk>
Cc: linux-kernel@lists.codethink.co.uk
Link: http://lkml.kernel.org/r/1466178974-7105-1-git-send-email-ben.dooks@codethink.co.uk
Signed-off-by: Thomas Gleixner <tglx@linutronix.de>
---
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 a9b76a4..2c5bc77 100644
--- a/kernel/time/clockevents.c
+++ b/kernel/time/clockevents.c
@@ -645,7 +645,7 @@ void tick_cleanup_dead_cpu(int cpu)
#endif
#ifdef CONFIG_SYSFS
-struct bus_type clockevents_subsys = {
+static struct bus_type clockevents_subsys = {
.name = "clockevents",
.dev_name = "clockevent",
};
prev parent reply other threads:[~2016-07-19 8:52 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-17 15:56 [PATCH] clockevents: make clockevents_subsys static Ben Dooks
2016-07-19 8:51 ` tip-bot for Ben Dooks [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=tip-775be506266a860f141f6b848c92c316c602a94f@git.kernel.org \
--to=tipbot@zytor.com \
--cc=ben.dooks@codethink.co.uk \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tip-commits@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=tglx@linutronix.de \
/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;
as well as URLs for NNTP newsgroup(s).