From: kbuild test robot <lkp@intel.com>
To: Hari Bathini <hbathini@linux.vnet.ibm.com>
Cc: kbuild-all@01.org, linux-kernel@vger.kernel.org,
fenghua.yu@intel.com, tony.luck@intel.com,
linux-ia64@vger.kernel.org, dyoung@redhat.com,
kexec@lists.infradead.org,
Mahesh J Salgaonkar <mahesh@linux.vnet.ibm.com>,
ebiederm@xmission.com, Michael Ellerman <mpe@ellerman.id.au>,
linuxppc-dev@lists.ozlabs.org, vgoyal@redhat.com
Subject: Re: [PATCH 1/3] crash: move crashkernel parsing and vmcore related code under CONFIG_CRASH_CORE
Date: Thu, 10 Nov 2016 21:51:38 +0800 [thread overview]
Message-ID: <201611102107.imfeZjH3%fengguang.wu@intel.com> (raw)
In-Reply-To: <147877904646.31483.2251653505359017982.stgit@hbathini.in.ibm.com>
[-- Attachment #1: Type: text/plain, Size: 3720 bytes --]
Hi Hari,
[auto build test WARNING on linus/master]
[also build test WARNING on v4.9-rc4]
[cannot apply to powerpc/next next-20161110]
[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/Hari-Bathini/kexec-fadump-remove-dependency-with-CONFIG_KEXEC-and-reuse-crashkernel-parameter-for-fadump/20161110-200330
config: h8300-h8300h-sim_defconfig (attached as .config)
compiler: h8300-linux-gcc (GCC) 6.2.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=h8300
All warnings (new ones prefixed by >>):
In file included from arch/h8300/include/asm/elf.h:8:0,
from include/linux/elfcore.h:6,
from include/linux/crash_core.h:5,
from include/linux/kexec.h:17,
from kernel/reboot.c:11:
>> arch/h8300/include/asm/ptrace.h:31:34: warning: 'struct task_struct' declared inside parameter list will not be visible outside of this definition or declaration
extern long h8300_get_reg(struct task_struct *task, int regno);
^~~~~~~~~~~
arch/h8300/include/asm/ptrace.h:32:33: warning: 'struct task_struct' declared inside parameter list will not be visible outside of this definition or declaration
extern int h8300_put_reg(struct task_struct *task, int regno,
^~~~~~~~~~~
vim +31 arch/h8300/include/asm/ptrace.h
d2a5f499 Yoshinori Sato 2015-05-11 15 #define H8300_REGS_NO 12
d2a5f499 Yoshinori Sato 2015-05-11 16 #endif
d2a5f499 Yoshinori Sato 2015-05-11 17
d2a5f499 Yoshinori Sato 2015-05-11 18 #define arch_has_single_step() (1)
d2a5f499 Yoshinori Sato 2015-05-11 19
d2a5f499 Yoshinori Sato 2015-05-11 20 #define user_mode(regs) (!((regs)->ccr & PS_S))
d2a5f499 Yoshinori Sato 2015-05-11 21 #define instruction_pointer(regs) ((regs)->pc)
d2a5f499 Yoshinori Sato 2015-05-11 22 #define profile_pc(regs) instruction_pointer(regs)
d2a5f499 Yoshinori Sato 2015-05-11 23 #define user_stack_pointer(regs) ((regs)->sp)
d2a5f499 Yoshinori Sato 2015-05-11 24 #define current_pt_regs() ((struct pt_regs *) \
d2a5f499 Yoshinori Sato 2015-05-11 25 (THREAD_SIZE + (unsigned long)current_thread_info()) - 1)
d2a5f499 Yoshinori Sato 2015-05-11 26 #define signal_pt_regs() ((struct pt_regs *)current->thread.esp0)
d2a5f499 Yoshinori Sato 2015-05-11 27 #define current_user_stack_pointer() rdusp()
d2a5f499 Yoshinori Sato 2015-05-11 28 #define task_pt_regs(task) \
d2a5f499 Yoshinori Sato 2015-05-11 29 ((struct pt_regs *) (task_stack_page(task) + THREAD_SIZE) - 1)
d2a5f499 Yoshinori Sato 2015-05-11 30
d2a5f499 Yoshinori Sato 2015-05-11 @31 extern long h8300_get_reg(struct task_struct *task, int regno);
d2a5f499 Yoshinori Sato 2015-05-11 32 extern int h8300_put_reg(struct task_struct *task, int regno,
d2a5f499 Yoshinori Sato 2015-05-11 33 unsigned long data);
d2a5f499 Yoshinori Sato 2015-05-11 34
d2a5f499 Yoshinori Sato 2015-05-11 35 #endif /* __ASSEMBLY__ */
d2a5f499 Yoshinori Sato 2015-05-11 36 #endif /* _H8300_PTRACE_H */
:::::: The code at line 31 was first introduced by commit
:::::: d2a5f4999f6c211adf30d9788349e13988d6f2a7 h8300: Assembly headers
:::::: TO: Yoshinori Sato <ysato@users.sourceforge.jp>
:::::: CC: Yoshinori Sato <ysato@users.sourceforge.jp>
---
0-DAY kernel test infrastructure Open Source Technology Center
https://lists.01.org/pipermail/kbuild-all Intel Corporation
[-- Attachment #2: .config.gz --]
[-- Type: application/gzip, Size: 4484 bytes --]
next prev parent reply other threads:[~2016-11-10 13:52 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-10 11:57 [PATCH 0/3] kexec/fadump: remove dependency with CONFIG_KEXEC and reuse crashkernel parameter for fadump Hari Bathini
2016-11-10 11:57 ` [PATCH 1/3] crash: move crashkernel parsing and vmcore related code under CONFIG_CRASH_CORE Hari Bathini
2016-11-10 13:51 ` kbuild test robot [this message]
2016-11-14 5:36 ` Baoquan He
2016-11-14 10:17 ` Hari Bathini
2016-11-10 11:57 ` [PATCH 2/3] powerpc/fadump: reuse crashkernel parameter for fadump memory reservation Hari Bathini
2016-11-10 11:58 ` [PATCH 3/3] powerpc/fadump: update documentation about crashkernel parameter reuse Hari Bathini
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=201611102107.imfeZjH3%fengguang.wu@intel.com \
--to=lkp@intel.com \
--cc=dyoung@redhat.com \
--cc=ebiederm@xmission.com \
--cc=fenghua.yu@intel.com \
--cc=hbathini@linux.vnet.ibm.com \
--cc=kbuild-all@01.org \
--cc=kexec@lists.infradead.org \
--cc=linux-ia64@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=mahesh@linux.vnet.ibm.com \
--cc=mpe@ellerman.id.au \
--cc=tony.luck@intel.com \
--cc=vgoyal@redhat.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