From: Fengguang Wu <fengguang.wu@intel.com>
To: kernel-janitors@vger.kernel.org
Subject: [signal:arch-m32r 1/2] arch/m32r/kernel/process.c:205:35: error: 'ret_from_kernel_thread' undeclared
Date: Tue, 16 Oct 2012 17:21:00 +0000 [thread overview]
Message-ID: <20121016172100.GA11813@localhost> (raw)
Hi Al,
FYI, kernel build failed on
tree: git://git.kernel.org/pub/scm/linux/kernel/git/viro/signal.git arch-m32r
head: ad256c8748f5a072a58c8e2f5cc8220ed01a2701
commit: 1e510c2fc8dd36525e49d6081aca3bbc33cd8f9c [1/2] m32r: switch to generic kernel_thread()/kernel_execve()
config: m32r-m32104ut_defconfig # make ARCH=m32r m32104ut_defconfig
All error/warnings:
arch/m32r/kernel/process.c: In function 'copy_thread':
arch/m32r/kernel/process.c:205:35: error: 'ret_from_kernel_thread' undeclared (first use in this function)
arch/m32r/kernel/process.c:205:35: note: each undeclared identifier is reported only once for each function it appears in
vim +205 arch/m32r/kernel/process.c
^1da177e Linus Torvalds 2005-04-16 199
1e510c2f Al Viro 2012-10-15 200 if (unlikely(!regs)) {
1e510c2f Al Viro 2012-10-15 201 memset(childregs, 0, sizeof(struct pt_regs));
1e510c2f Al Viro 2012-10-15 202 childregs->psw = M32R_PSW_BIE;
1e510c2f Al Viro 2012-10-15 203 childregs->r1 = spu; /* fn */
1e510c2f Al Viro 2012-10-15 204 childregs->r0 = arg;
1e510c2f Al Viro 2012-10-15 @205 tsk->thread.lr = (unsigned long)ret_from_kernel_thread;
1e510c2f Al Viro 2012-10-15 206 } else {
1e510c2f Al Viro 2012-10-15 207 /* Copy registers */
1e510c2f Al Viro 2012-10-15 208 *childregs = *regs;
---
0-DAY kernel build testing backend Open Source Technology Center
Fengguang Wu, Yuanhan Liu Intel Corporation
reply other threads:[~2012-10-16 17:21 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=20121016172100.GA11813@localhost \
--to=fengguang.wu@intel.com \
--cc=kernel-janitors@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.