From: kernel test robot <lkp@intel.com>
To: kbuild-all@lists.01.org
Subject: [ak:lto-5.13-1-wip 36/36] arch/x86/kernel/paravirt.c:127:15: warning: no previous prototype for 'native_steal_clock'
Date: Mon, 26 Apr 2021 11:35:56 +0800 [thread overview]
Message-ID: <202104261153.eVdi61jO-lkp@intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1584 bytes --]
tree: https://git.kernel.org/pub/scm/linux/kernel/git/ak/linux-misc.git lto-5.13-1-wip
head: 45fc24254df69291f9ebd597bc747df2eb61ee3a
commit: 45fc24254df69291f9ebd597bc747df2eb61ee3a [36/36] x86/paravirt/lto: Export native_steal_clock
config: x86_64-randconfig-s022-20210426 (attached as .config)
compiler: gcc-9 (Debian 9.3.0-22) 9.3.0
reproduce:
# apt-get install sparse
# sparse version: v0.6.3-341-g8af24329-dirty
# https://git.kernel.org/pub/scm/linux/kernel/git/ak/linux-misc.git/commit/?id=45fc24254df69291f9ebd597bc747df2eb61ee3a
git remote add ak https://git.kernel.org/pub/scm/linux/kernel/git/ak/linux-misc.git
git fetch --no-tags ak lto-5.13-1-wip
git checkout 45fc24254df69291f9ebd597bc747df2eb61ee3a
# save the attached .config to linux build tree
make W=1 C=1 CF='-fdiagnostic-prefix -D__CHECK_ENDIAN__' W=1 ARCH=x86_64
If you fix the issue, kindly add following tag as appropriate
Reported-by: kernel test robot <lkp@intel.com>
All warnings (new ones prefixed by >>):
>> arch/x86/kernel/paravirt.c:127:15: warning: no previous prototype for 'native_steal_clock' [-Wmissing-prototypes]
127 | __visible u64 native_steal_clock(int cpu)
| ^~~~~~~~~~~~~~~~~~
vim +/native_steal_clock +127 arch/x86/kernel/paravirt.c
126
> 127 __visible u64 native_steal_clock(int cpu)
128 {
129 return 0;
130 }
131
---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all(a)lists.01.org
[-- Attachment #2: config.gz --]
[-- Type: application/gzip, Size: 28275 bytes --]
reply other threads:[~2021-04-26 3:35 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=202104261153.eVdi61jO-lkp@intel.com \
--to=lkp@intel.com \
--cc=kbuild-all@lists.01.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 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.