From: kernel test robot <lkp@intel.com>
To: Vineeth Pillai <viremana@linux.microsoft.com>,
Haiyang Zhang <haiyangz@microsoft.com>,
Stephen Hemminger <sthemmin@microsoft.com>,
Wei Liu <wei.liu@kernel.org>
Cc: kbuild-all@lists.01.org,
Vineeth Pillai <viremana@linux.microsoft.com>,
"K . Y . Srinivasan" <kys@microsoft.com>,
linux-hyperv@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] hv_utils: return error if host timesysnc update is stale
Date: Thu, 20 Aug 2020 06:19:51 +0800 [thread overview]
Message-ID: <202008200619.WJEj2Ns2%lkp@intel.com> (raw)
In-Reply-To: <20200819174527.47156-1-viremana@linux.microsoft.com>
[-- Attachment #1: Type: text/plain, Size: 1377 bytes --]
Hi Vineeth,
Thank you for the patch! Perhaps something to improve:
[auto build test WARNING on linus/master]
[also build test WARNING on v5.9-rc1 next-20200819]
[If your patch is applied to the wrong git tree, kindly drop us a note.
And when submitting patch, we suggest to use '--base' as documented in
https://git-scm.com/docs/git-format-patch]
url: https://github.com/0day-ci/linux/commits/Vineeth-Pillai/hv_utils-return-error-if-host-timesysnc-update-is-stale/20200820-014742
base: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git 18445bf405cb331117bc98427b1ba6f12418ad17
config: i386-randconfig-s001-20200818 (attached as .config)
compiler: gcc-9 (Debian 9.3.0-15) 9.3.0
reproduce:
# apt-get install sparse
# sparse version: v0.6.2-183-gaa6ede3b-dirty
# save the attached .config to linux build tree
make W=1 C=1 CF='-fdiagnostic-prefix -D__CHECK_ENDIAN__' ARCH=i386
If you fix the issue, kindly add following tag as appropriate
Reported-by: kernel test robot <lkp@intel.com>
sparse warnings: (new ones prefixed by >>)
>> drivers/hv/hv_util.c:293:11: sparse: sparse: symbol 'HOST_TIMESYNC_DELAY_THRESH' was not declared. Should it be static?
Please review and possibly fold the followup patch.
---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all@lists.01.org
[-- Attachment #2: .config.gz --]
[-- Type: application/gzip, Size: 38967 bytes --]
next prev parent reply other threads:[~2020-08-19 22:20 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-19 17:45 Vineeth Pillai
2020-08-19 22:19 ` kernel test robot [this message]
2020-08-19 22:19 ` [RFC PATCH] hv_utils: HOST_TIMESYNC_DELAY_THRESH can be static kernel test robot
2020-08-19 22:54 ` [PATCH] hv_utils: return error if host timesysnc update is stale kernel test robot
2020-08-20 18:21 ` Michael Kelley
2020-08-20 21:39 ` Vineeth Pillai
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=202008200619.WJEj2Ns2%lkp@intel.com \
--to=lkp@intel.com \
--cc=haiyangz@microsoft.com \
--cc=kbuild-all@lists.01.org \
--cc=kys@microsoft.com \
--cc=linux-hyperv@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sthemmin@microsoft.com \
--cc=viremana@linux.microsoft.com \
--cc=wei.liu@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
Powered by JetHome