From: kbuild test robot <lkp@intel.com>
To: Jeffrey Merkey <jeffmerkey@gmail.com>
Cc: kbuild-all@01.org, linux-kernel@vger.kernel.org,
geert@linux-m68k.org, linux.mdb@gmail.com,
linux-m68k@lists.linux-m68k.org
Subject: Re: [PATCH 27/31] Add debugger entry points for M68K
Date: Fri, 29 Jan 2016 05:24:12 +0800 [thread overview]
Message-ID: <201601290527.dAz1250i%fengguang.wu@intel.com> (raw)
In-Reply-To: <1454010458-29525-1-git-send-email-jeffmerkey@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 3210 bytes --]
Hi Jeffrey,
[auto build test ERROR on v4.5-rc1]
[also build test ERROR on next-20160128]
[cannot apply to tip/x86/core]
[if your patch is applied to the wrong git tree, please drop us a note to help improving the system]
url: https://github.com/0day-ci/linux/commits/Jeffrey-Merkey/Add-hard-soft-lockup-debugger-entry-points/20160129-035852
config: m68k-sun3_defconfig (attached as .config)
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=m68k
All error/warnings (new ones prefixed by >>):
In file included from kernel/notifier.c:1:0:
>> include/linux/kdebug.h:20:16: warning: 'enum die_val' declared inside parameter list
struct pt_regs *regs, long err, int trap, int sig);
^
>> include/linux/kdebug.h:20:16: warning: its scope is only this definition or declaration, which is probably not what you want
>> kernel/notifier.c:537:16: warning: 'enum die_val' declared inside parameter list
struct pt_regs *regs, long err, int trap, int sig)
^
>> kernel/notifier.c:536:37: error: parameter 1 ('val') has incomplete type
int notrace notify_die(enum die_val val, const char *str,
^
kernel/notifier.c: In function 'notify_die':
>> kernel/notifier.c:550:1: warning: control reaches end of non-void function [-Wreturn-type]
}
^
vim +20 include/linux/kdebug.h
1eeb66a1 Christoph Hellwig 2007-05-08 4 #include <asm/kdebug.h>
1eeb66a1 Christoph Hellwig 2007-05-08 5
fe9844d5 Andrew Morton 2007-07-31 6 struct notifier_block;
fe9844d5 Andrew Morton 2007-07-31 7
1eeb66a1 Christoph Hellwig 2007-05-08 8 struct die_args {
1eeb66a1 Christoph Hellwig 2007-05-08 9 struct pt_regs *regs;
1eeb66a1 Christoph Hellwig 2007-05-08 10 const char *str;
1eeb66a1 Christoph Hellwig 2007-05-08 11 long err;
1eeb66a1 Christoph Hellwig 2007-05-08 12 int trapnr;
1eeb66a1 Christoph Hellwig 2007-05-08 13 int signr;
1eeb66a1 Christoph Hellwig 2007-05-08 14 };
1eeb66a1 Christoph Hellwig 2007-05-08 15
1eeb66a1 Christoph Hellwig 2007-05-08 16 int register_die_notifier(struct notifier_block *nb);
1eeb66a1 Christoph Hellwig 2007-05-08 17 int unregister_die_notifier(struct notifier_block *nb);
1eeb66a1 Christoph Hellwig 2007-05-08 18
1eeb66a1 Christoph Hellwig 2007-05-08 19 int notify_die(enum die_val val, const char *str,
1eeb66a1 Christoph Hellwig 2007-05-08 @20 struct pt_regs *regs, long err, int trap, int sig);
1eeb66a1 Christoph Hellwig 2007-05-08 21
1eeb66a1 Christoph Hellwig 2007-05-08 22 #endif /* _LINUX_KDEBUG_H */
:::::: The code at line 20 was first introduced by commit
:::::: 1eeb66a1bb973534dc3d064920a5ca683823372e move die notifier handling to common code
:::::: TO: Christoph Hellwig <hch@lst.de>
:::::: CC: Linus Torvalds <torvalds@woody.linux-foundation.org>
---
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: 11218 bytes --]
prev parent reply other threads:[~2016-01-28 21:24 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-28 19:47 [PATCH 27/31] Add debugger entry points for M68K Jeffrey Merkey
2016-01-28 20:40 ` Geert Uytterhoeven
2016-01-28 20:43 ` Jeffrey Merkey
2016-01-28 21:24 ` kbuild test robot [this message]
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=201601290527.dAz1250i%fengguang.wu@intel.com \
--to=lkp@intel.com \
--cc=geert@linux-m68k.org \
--cc=jeffmerkey@gmail.com \
--cc=kbuild-all@01.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-m68k@lists.linux-m68k.org \
--cc=linux.mdb@gmail.com \
/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