From: Stephen Rothwell <sfr@canb.auug.org.au>
To: David Howells <dhowells@redhat.com>
Cc: linux-next@vger.kernel.org, linux-kernel@vger.kernel.org,
Linus <torvalds@linux-foundation.org>,
"David S. Miller" <davem@davemloft.net>
Subject: linux-next: build failure after merge of the final tree (Linus' tree related)
Date: Fri, 30 Mar 2012 14:31:56 +1100 [thread overview]
Message-ID: <20120330143156.6c55bd32d207a074f65d1b16@canb.auug.org.au> (raw)
[-- Attachment #1: Type: text/plain, Size: 1596 bytes --]
Hi all,
After merging the final tree, today's linux-next build (sparc64 defconfig)
failed like this:
kernel/signal.c: In function 'ptrace_stop':
kernel/signal.c:1860:3: error: implicit declaration of function 'synchronize_user_stack' [-Werror=implicit-function-declaration]
Presumably caused by commit d550bbd40c0e ("Disintegrate asm/system.h for
Sparc").
I added this patch for today:
From: Stephen Rothwell <sfr@canb.auug.org.au>
Date: Fri, 30 Mar 2012 14:26:24 +1100
Subject: [PATCH] sparc: fix fallout from system.h split
Fixes this build error:
kernel/signal.c: In function 'ptrace_stop':
kernel/signal.c:1860:3: error: implicit declaration of function 'synchronize_user_stack' [-Werror=implicit-function-declaration]
Signed-off-by: Stephen Rothwell <sfr@canb.auug.org.au>
---
arch/sparc/include/asm/ptrace.h | 3 +++
1 file changed, 3 insertions(+)
diff --git a/arch/sparc/include/asm/ptrace.h b/arch/sparc/include/asm/ptrace.h
index ef8c7c0..8112096 100644
--- a/arch/sparc/include/asm/ptrace.h
+++ b/arch/sparc/include/asm/ptrace.h
@@ -165,6 +165,7 @@ struct sparc_stackf {
#ifdef __KERNEL__
#include <linux/threads.h>
+#include <asm/switch_to.h>
static inline int pt_regs_trap_type(struct pt_regs *regs)
{
@@ -241,6 +242,8 @@ extern unsigned long profile_pc(struct pt_regs *);
#ifdef __KERNEL__
+#include <asm/switch_to.h>
+
static inline bool pt_regs_is_syscall(struct pt_regs *regs)
{
return (regs->psr & PSR_SYSCALL);
--
1.7.9.5
--
Cheers,
Stephen Rothwell sfr@canb.auug.org.au
[-- Attachment #2: Type: application/pgp-signature, Size: 836 bytes --]
next reply other threads:[~2012-03-30 3:32 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-30 3:31 Stephen Rothwell [this message]
2012-03-30 3:39 ` linux-next: build failure after merge of the final tree (Linus' tree related) David Miller
2012-03-30 5:45 ` David Miller
2012-03-30 6:31 ` Stephen Rothwell
-- strict thread matches above, loose matches on Subject: below --
2013-03-21 6:23 linux-next: build failure after merge of the final tree (linus' " Stephen Rothwell
2011-08-29 5:47 Stephen Rothwell
2011-08-29 16:22 ` David Miller
2011-06-17 5:38 linux-next: build failure after merge of the final tree (Linus' " Stephen Rothwell
2011-06-17 5:34 ` KAMEZAWA Hiroyuki
2011-01-15 2:34 linux-next: build failure after merge of the final tree (linus' " Stephen Rothwell
2011-01-15 13:19 ` Rafael J. Wysocki
2011-01-15 15:44 ` Stephen Rothwell
2011-01-15 20:01 ` Rafael J. Wysocki
2010-07-22 3:58 linux-next: build failure after merge of the final tree (Linus' " Stephen Rothwell
2010-05-28 5:08 linux-next: build failure after merge of the final tree (linus' " Stephen Rothwell
2010-05-28 12:50 ` Steven Rostedt
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=20120330143156.6c55bd32d207a074f65d1b16@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=davem@davemloft.net \
--cc=dhowells@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=torvalds@linux-foundation.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;
as well as URLs for NNTP newsgroup(s).