From: kbuild test robot <lkp@intel.com>
To: Tianyu Lan <Tianyu.Lan@microsoft.com>
Cc: kbuild-all@01.org, linux-kernel@vger.kernel.org,
tipbuild@zytor.com, Thomas Gleixner <tglx@linutronix.de>,
Michael Kelley <mikelley@microsoft.com>
Subject: [tip:timers/core 34/34] drivers//clocksource/hyperv_timer.c:264:35: error: 'hv_sched_clock_offset' undeclared; did you mean 'sched_clock_register'?
Date: Thu, 22 Aug 2019 10:25:20 +0800 [thread overview]
Message-ID: <201908221019.hX9jqUFa%lkp@intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 2097 bytes --]
tree: https://kernel.googlesource.com/pub/scm/linux/kernel/git/tip/tip.git timers/core
head: b74e1d61dbc614ff35ef3ad9267c61ed06b09051
commit: b74e1d61dbc614ff35ef3ad9267c61ed06b09051 [34/34] clocksource/hyperv: Add Hyper-V specific sched clock function
config: i386-randconfig-g002-201933 (attached as .config)
compiler: gcc-7 (Debian 7.4.0-10) 7.4.0
reproduce:
git checkout b74e1d61dbc614ff35ef3ad9267c61ed06b09051
# save the attached .config to linux build tree
make ARCH=i386
If you fix the issue, kindly add following tag
Reported-by: kbuild test robot <lkp@intel.com>
All error/warnings (new ones prefixed by >>):
drivers//clocksource/hyperv_timer.c: In function 'read_hv_sched_clock_msr':
>> drivers//clocksource/hyperv_timer.c:264:35: error: 'hv_sched_clock_offset' undeclared (first use in this function); did you mean 'sched_clock_register'?
return read_hv_clock_msr(NULL) - hv_sched_clock_offset;
^~~~~~~~~~~~~~~~~~~~~
sched_clock_register
drivers//clocksource/hyperv_timer.c:264:35: note: each undeclared identifier is reported only once for each function it appears in
drivers//clocksource/hyperv_timer.c: In function 'hv_init_clocksource':
drivers//clocksource/hyperv_timer.c:334:2: error: 'hv_sched_clock_offset' undeclared (first use in this function); did you mean 'sched_clock_register'?
hv_sched_clock_offset = hyperv_cs->read(hyperv_cs);
^~~~~~~~~~~~~~~~~~~~~
sched_clock_register
drivers//clocksource/hyperv_timer.c: In function 'read_hv_sched_clock_msr':
>> drivers//clocksource/hyperv_timer.c:265:1: warning: control reaches end of non-void function [-Wreturn-type]
}
^
vim +264 drivers//clocksource/hyperv_timer.c
261
262 static u64 read_hv_sched_clock_msr(void)
263 {
> 264 return read_hv_clock_msr(NULL) - hv_sched_clock_offset;
> 265 }
266
---
0-DAY kernel test infrastructure Open Source Technology Center
https://lists.01.org/pipermail/kbuild-all Intel Corporation
[-- Attachment #2: .config.gz --]
[-- Type: application/gzip, Size: 32583 bytes --]
next reply other threads:[~2019-08-22 2:26 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-22 2:25 kbuild test robot [this message]
2019-08-22 3:11 ` Tianyu Lan
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=201908221019.hX9jqUFa%lkp@intel.com \
--to=lkp@intel.com \
--cc=Tianyu.Lan@microsoft.com \
--cc=kbuild-all@01.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mikelley@microsoft.com \
--cc=tglx@linutronix.de \
--cc=tipbuild@zytor.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
all inboxes | Powered by JetHome®