From: kernel test robot <lkp@intel.com>
To: brookxu <brookxu.cn@gmail.com>,
adobriyan@gmail.com, bsingharora@gmail.com,
akpm@linux-foundation.org, ebiederm@xmission.com,
linux-kernel@vger.kernel.org
Cc: kbuild-all@lists.01.org
Subject: Re: [RESEND PATCH 2/2] delayacct: Add a proc file to dump the delay info
Date: Tue, 13 Apr 2021 14:14:18 +0800 [thread overview]
Message-ID: <202104131324.KWYCGyaZ-lkp@intel.com> (raw)
In-Reply-To: <99fd223ec19a6bc17fa5b39aaf6aed6cbdbea722.1618275619.git.brookxu@tencent.com>
[-- Attachment #1: Type: text/plain, Size: 1709 bytes --]
Hi brookxu,
Thank you for the patch! Perhaps something to improve:
[auto build test WARNING on linus/master]
[also build test WARNING on v5.12-rc7 next-20210412]
[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/brookxu/delayacct-refactor-the-code-to-simplify-the-implementation/20210413-093934
base: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git 89698becf06d341a700913c3d89ce2a914af69a2
config: x86_64-randconfig-s021-20210413 (attached as .config)
compiler: gcc-9 (Debian 9.3.0-22) 9.3.0
reproduce:
# apt-get install sparse
# sparse version: v0.6.3-280-g2cd6d34e-dirty
# https://github.com/0day-ci/linux/commit/7023a409dec95195a0e3360a36e8cb66363a9457
git remote add linux-review https://github.com/0day-ci/linux
git fetch --no-tags linux-review brookxu/delayacct-refactor-the-code-to-simplify-the-implementation/20210413-093934
git checkout 7023a409dec95195a0e3360a36e8cb66363a9457
# save the attached .config to linux build tree
make W=1 C=1 CF='-fdiagnostic-prefix -D__CHECK_ENDIAN__' ARCH=x86_64
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 >>)
>> kernel/delayacct.c:35:23: sparse: sparse: symbol 'delayacct_stats' 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: 36937 bytes --]
next prev parent reply other threads:[~2021-04-13 6:15 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-13 1:37 [RESEND PATCH 1/2] delayacct: refactor the code to simplify the implementation brookxu
2021-04-13 1:37 ` [RESEND PATCH 2/2] delayacct: Add a proc file to dump the delay info brookxu
2021-04-13 6:14 ` kernel test robot [this message]
2021-04-13 6:14 ` [RFC PATCH] delayacct: delayacct_stats[] can be static kernel test robot
2021-04-13 21:26 ` [RESEND PATCH 2/2] delayacct: Add a proc file to dump the delay info kernel test robot
2021-04-13 23:19 ` [RESEND PATCH 1/2] delayacct: refactor the code to simplify the implementation kernel test robot
2021-04-14 1:24 ` kernel test robot
2021-04-19 7:01 ` Balbir Singh
2021-04-19 9:30 ` brookxu
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=202104131324.KWYCGyaZ-lkp@intel.com \
--to=lkp@intel.com \
--cc=adobriyan@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=brookxu.cn@gmail.com \
--cc=bsingharora@gmail.com \
--cc=ebiederm@xmission.com \
--cc=kbuild-all@lists.01.org \
--cc=linux-kernel@vger.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