From: kbuild test robot <fengguang.wu@intel.com>
To: Ingo Molnar <mingo@kernel.org>
Cc: kbuild-all@01.org, linux-kernel@vger.kernel.org, tipbuild@zytor.com
Subject: [tip:WIP.sched/core 98/154] arch/mips/include/asm/processor.h:384:41: error: implicit declaration of function 'task_stack_page'
Date: Sun, 12 Feb 2017 08:23:01 +0800 [thread overview]
Message-ID: <201702120855.uSyMFW20%fengguang.wu@intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 2976 bytes --]
tree: https://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git WIP.sched/core
head: 12372f63e2728a509817b56878cd6633d92053b3
commit: 030a6259fec4df48769d8efc0e0d4431e05935aa [98/154] sched/headers: Move task-stack related APIs from <linux/sched.h> to <linux/sched/task_stack.h>
config: mips-generic_defconfig (attached as .config)
compiler: mipsel-linux-gnu-gcc (Debian 6.1.1-9) 6.1.1 20160705
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
git checkout 030a6259fec4df48769d8efc0e0d4431e05935aa
# save the attached .config to linux build tree
make.cross ARCH=mips
All errors (new ones prefixed by >>):
In file included from arch/mips/include/asm/io.h:28:0,
from include/linux/io.h:25,
from arch/mips/kernel/smp-cps.c:12:
arch/mips/kernel/smp-cps.c: In function 'cps_boot_secondary':
>> arch/mips/include/asm/processor.h:384:41: error: implicit declaration of function 'task_stack_page' [-Werror=implicit-function-declaration]
#define __KSTK_TOS(tsk) ((unsigned long)task_stack_page(tsk) + \
^
arch/mips/kernel/smp-cps.c:302:16: note: in expansion of macro '__KSTK_TOS'
vpe_cfg->sp = __KSTK_TOS(idle);
^~~~~~~~~~
cc1: some warnings being treated as errors
vim +/task_stack_page +384 arch/mips/include/asm/processor.h
04cc89d1 arch/mips/include/asm/processor.h Ralf Baechle 2016-03-27 378 static inline void flush_thread(void)
04cc89d1 arch/mips/include/asm/processor.h Ralf Baechle 2016-03-27 379 {
04cc89d1 arch/mips/include/asm/processor.h Ralf Baechle 2016-03-27 380 }
04cc89d1 arch/mips/include/asm/processor.h Ralf Baechle 2016-03-27 381
^1da177e include/asm-mips/processor.h Linus Torvalds 2005-04-16 382 unsigned long get_wchan(struct task_struct *p);
^1da177e include/asm-mips/processor.h Linus Torvalds 2005-04-16 383
484889fc arch/mips/include/asm/processor.h David Daney 2009-07-08 @384 #define __KSTK_TOS(tsk) ((unsigned long)task_stack_page(tsk) + \
484889fc arch/mips/include/asm/processor.h David Daney 2009-07-08 385 THREAD_SIZE - 32 - sizeof(struct pt_regs))
484889fc arch/mips/include/asm/processor.h David Daney 2009-07-08 386 #define task_pt_regs(tsk) ((struct pt_regs *)__KSTK_TOS(tsk))
40bc9c67 include/asm-mips/processor.h Al Viro 2006-01-12 387 #define KSTK_EIP(tsk) (task_pt_regs(tsk)->cp0_epc)
:::::: The code at line 384 was first introduced by commit
:::::: 484889fc85a223ef56edc31828b86751b2296b7c MIPS: Avoid clobbering struct pt_regs in kthreads
:::::: TO: David Daney <ddaney@caviumnetworks.com>
:::::: CC: Ralf Baechle <ralf@linux-mips.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/gzip, Size: 10813 bytes --]
reply other threads:[~2017-02-12 0:23 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=201702120855.uSyMFW20%fengguang.wu@intel.com \
--to=fengguang.wu@intel.com \
--cc=kbuild-all@01.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=tipbuild@zytor.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
all inboxes | Powered by JetHome®