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: Re: [PATCH v2 1/1] x86/init: Noop get/set wallclock when platform doesn't support RTC
Date: Fri, 30 Aug 2019 02:51:35 +0800 [thread overview]
Message-ID: <201908300248.W8vwpC3z%lkp@intel.com> (raw)
In-Reply-To: <199d34bc514d4fbf2058a862918dc6a71390c48f.1566895445.git.rahul.tanwar@linux.intel.com>
Hi Rahul,
Thank you for the patch! Perhaps something to improve:
[auto build test WARNING on linus/master]
[cannot apply to v5.3-rc6 next-20190829]
[if your patch is applied to the wrong git tree, please drop us a note to help improve the system]
url: https://github.com/0day-ci/linux/commits/Rahul-Tanwar/x86-init-Noop-get-set-wallclock-when-platform-doesn-t-support-RTC/20190829-202237
reproduce:
# apt-get install sparse
# sparse version: v0.6.1-rc1-7-g2b96cd8-dirty
make ARCH=x86_64 allmodconfig
make C=1 CF='-fdiagnostic-prefix -D__CHECK_ENDIAN__'
If you fix the issue, kindly add following tag
Reported-by: kbuild test robot <lkp@intel.com>
sparse warnings: (new ones prefixed by >>)
>> arch/x86/kernel/x86_init.c:42:6: sparse: sparse: symbol 'x86_wallclock_init' was not declared. Should it be static?
Please review and possibly fold the followup patch.
---
0-DAY kernel test infrastructure Open Source Technology Center
https://lists.01.org/pipermail/kbuild-all Intel Corporation
next 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 [this message]
2019-08-29 18:51 ` [RFC PATCH] x86/init: x86_wallclock_init() can be static kbuild test robot
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=201908300248.W8vwpC3z%lkp@intel.com \
--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