From: kbuild test robot <lkp@intel.com>
To: Andi Kleen <andi@firstfloor.org>
Cc: kbuild-all@01.org, akpm@linux-foundation.org,
linux-kernel@vger.kernel.org, Andi Kleen <ak@linux.intel.com>
Subject: Re: [PATCH] Support resetting WARN*_ONCE
Date: Wed, 3 Aug 2016 12:12:25 +0800 [thread overview]
Message-ID: <201608031201.IIYHSxBH%fengguang.wu@intel.com> (raw)
In-Reply-To: <1470170405-21530-1-git-send-email-andi@firstfloor.org>
[-- Attachment #1: Type: text/plain, Size: 1712 bytes --]
Hi Andi,
[auto build test ERROR on asm-generic/master]
[also build test ERROR on v4.7 next-20160802]
[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/Andi-Kleen/Support-resetting-WARN-_ONCE/20160803-112312
base: https://git.kernel.org/pub/scm/linux/kernel/git/arnd/asm-generic.git master
config: xtensa-allmodconfig (attached as .config)
compiler: xtensa-linux-gcc (GCC) 4.9.0
reproduce:
wget https://git.kernel.org/cgit/linux/kernel/git/wfg/lkp-tests.git/plain/sbin/make.cross -O ~/bin/make.cross
chmod +x ~/bin/make.cross
# save the attached .config to linux build tree
make.cross ARCH=xtensa
All errors (new ones prefixed by >>):
kernel/panic.c: In function 'clear_warn_once_set':
>> kernel/panic.c:557:9: error: '__start_once' undeclared (first use in this function)
memset(__start_once, 0, __end_once - __start_once);
^
kernel/panic.c:557:9: note: each undeclared identifier is reported only once for each function it appears in
>> kernel/panic.c:557:26: error: '__end_once' undeclared (first use in this function)
memset(__start_once, 0, __end_once - __start_once);
^
vim +/__start_once +557 kernel/panic.c
551 #endif
552
553 /* Support resetting WARN*_ONCE state */
554
555 static int clear_warn_once_set(void *data, u64 val)
556 {
> 557 memset(__start_once, 0, __end_once - __start_once);
558 return 0;
559 }
560
---
0-DAY kernel test infrastructure Open Source Technology Center
https://lists.01.org/pipermail/kbuild-all Intel Corporation
[-- Attachment #2: .config.gz --]
[-- Type: application/octet-stream, Size: 44813 bytes --]
next prev parent reply other threads:[~2016-08-03 4:16 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-02 20:40 Andi Kleen
2016-08-03 4:12 ` kbuild test robot [this message]
2017-10-17 21:40 Andi Kleen
2017-10-17 21:54 ` Andrew Morton
2017-10-17 22:11 ` Andi Kleen
2017-10-18 5:35 ` Michael Ellerman
2017-10-19 20:47 ` Andi Kleen
2017-11-03 9:39 ` Michael Ellerman
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=201608031201.IIYHSxBH%fengguang.wu@intel.com \
--to=lkp@intel.com \
--cc=ak@linux.intel.com \
--cc=akpm@linux-foundation.org \
--cc=andi@firstfloor.org \
--cc=kbuild-all@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
all inboxes | Powered by JetHome®