From: kbuild test robot <lkp@intel.com>
To: Rahul Tanwar <rahul.tanwar@linux.intel.com>
Cc: kbuild-all@01.org, tglx@linutronix.de, mingo@redhat.com,
bp@alien8.de, hpa@zytor.com, tony.luck@intel.com, x86@kernel.org,
andriy.shevchenko@intel.com, alan@linux.intel.com,
linux-kernel@vger.kernel.org, qi-ming.wu@intel.com,
chuanhua.lei@linux.intel.com, cheol.yong.kim@intel.com,
rahul.tanwar@intel.com,
Rahul Tanwar <rahul.tanwar@linux.intel.com>
Subject: [RFC PATCH] x86/init: x86_wallclock_init() can be static
Date: Fri, 30 Aug 2019 02:51:36 +0800 [thread overview]
Message-ID: <20190829185136.pat4kgnolbsxjm3u@48261080c7f1> (raw)
In-Reply-To: <199d34bc514d4fbf2058a862918dc6a71390c48f.1566895445.git.rahul.tanwar@linux.intel.com>
Fixes: 1461badd03e7 ("x86/init: Noop get/set wallclock when platform doesn't support RTC")
Signed-off-by: kbuild test robot <lkp@intel.com>
---
x86_init.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/arch/x86/kernel/x86_init.c b/arch/x86/kernel/x86_init.c
index 88c120710d5d5..50aa8257fd20a 100644
--- a/arch/x86/kernel/x86_init.c
+++ b/arch/x86/kernel/x86_init.c
@@ -39,7 +39,7 @@ static const struct of_device_id of_cmos_match[] = {
{}
};
-void x86_wallclock_init(void)
+static void x86_wallclock_init(void)
{
struct device_node *node;
prev parent reply other threads:[~2019-08-29 18:52 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-27 9:26 [PATCH v2 0/1] Add option to skip using RTC Rahul Tanwar
2019-08-27 9:26 ` [PATCH v2 1/1] x86/init: Noop get/set wallclock when platform doesn't support RTC Rahul Tanwar
2019-08-29 18:51 ` kbuild test robot
2019-08-29 18:51 ` kbuild test robot [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=20190829185136.pat4kgnolbsxjm3u@48261080c7f1 \
--to=lkp@intel.com \
--cc=alan@linux.intel.com \
--cc=andriy.shevchenko@intel.com \
--cc=bp@alien8.de \
--cc=cheol.yong.kim@intel.com \
--cc=chuanhua.lei@linux.intel.com \
--cc=hpa@zytor.com \
--cc=kbuild-all@01.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=qi-ming.wu@intel.com \
--cc=rahul.tanwar@intel.com \
--cc=rahul.tanwar@linux.intel.com \
--cc=tglx@linutronix.de \
--cc=tony.luck@intel.com \
--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;
as well as URLs for NNTP newsgroup(s).