From: Stephen Rothwell <sfr@canb•auug.org.au>
To: Thomas Gleixner <tglx@linutronix•de>, Ingo Molnar <mingo@elte•hu>,
"H. Peter Anvin" <hpa@zytor•com>
Cc: linux-next@vger•kernel.org,
"David S. Miller" <davem@davemloft•net>,
Darren Hart <dvhltc@us•ibm.com>
Subject: linux-next: sparc tree build failure
Date: Thu, 9 Apr 2009 15:17:22 +1000 [thread overview]
Message-ID: <20090409151722.c8eabb56.sfr@canb.auug.org.au> (raw)
Hi all,
Today's linux-next build (sparc64 defconfig) failed like this:
arch/sparc/kernel/built-in.o: In function `trap_init':
(.init.text+0x4): undefined reference to `thread_info_offsets_are_bolixed_dave'
Caused by commit 52400ba946759af28442dee6265c5c0180ac7122 ("futex: add
requeue_pi functionality") (from the tip-core tree) which changed the
size of struct restart_block.
Dave, this might be a good time to suggest that sparc64 create its TI_
offsets automatically via asm-offsets ...
I applied the following patch for today.
--
Cheers,
Stephen Rothwell sfr@canb•auug.org.au
http://www.canb.auug.org.au/~sfr/
>From 11f2623cf0416509193865acad7e36ae05e31b1a Mon Sep 17 00:00:00 2001
From: Stephen Rothwell <sfr@canb•auug.org.au>
Date: Thu, 9 Apr 2009 15:12:38 +1000
Subject: [PATCH] sparc64: update for restart_block size change
Signed-off-by: Stephen Rothwell <sfr@canb•auug.org.au>
---
arch/sparc/include/asm/thread_info_64.h | 4 ++--
1 files changed, 2 insertions(+), 2 deletions(-)
diff --git a/arch/sparc/include/asm/thread_info_64.h b/arch/sparc/include/asm/thread_info_64.h
index 639ac80..6586572 100644
--- a/arch/sparc/include/asm/thread_info_64.h
+++ b/arch/sparc/include/asm/thread_info_64.h
@@ -102,8 +102,8 @@ struct thread_info {
#define TI_KERN_CNTD1 0x00000488
#define TI_PCR 0x00000490
#define TI_RESTART_BLOCK 0x00000498
-#define TI_KUNA_REGS 0x000004c0
-#define TI_KUNA_INSN 0x000004c8
+#define TI_KUNA_REGS 0x000004c8
+#define TI_KUNA_INSN 0x000004d0
#define TI_FPREGS 0x00000500
/* We embed this in the uppermost byte of thread_info->flags */
--
1.6.2.1
next reply other threads:[~2009-04-09 5:17 UTC|newest]
Thread overview: 46+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-09 5:17 Stephen Rothwell [this message]
2009-04-09 5:27 ` linux-next: sparc tree build failure Ingo Molnar
2009-04-09 5:28 ` David Miller
2009-04-09 5:36 ` Ingo Molnar
2009-04-09 5:40 ` David Miller
2009-04-09 5:53 ` Ingo Molnar
2009-04-09 5:59 ` David Miller
2009-04-09 5:28 ` David Miller
2009-04-14 3:45 ` Stephen Rothwell
-- strict thread matches above, loose matches on Subject: below --
2009-11-26 9:16 Stephen Rothwell
2009-11-26 23:28 ` David Miller
2009-11-27 9:00 ` Thomas Gleixner
2009-11-06 7:02 Stephen Rothwell
2009-11-06 8:19 ` David Miller
2009-11-06 8:26 ` David Miller
2009-11-06 8:27 ` David Miller
2009-11-07 2:35 ` Stephen Rothwell
2009-11-05 7:50 Stephen Rothwell
2009-11-05 7:53 ` David Miller
2009-11-05 8:00 ` David Miller
2009-11-05 14:44 ` Kristoffer Glembo
2009-11-13 10:34 ` Kristoffer Glembo
2009-11-13 14:57 ` David Miller
2009-10-05 7:43 Stephen Rothwell
2009-10-05 7:45 ` David Miller
2008-12-04 8:54 Stephen Rothwell
2008-12-04 11:47 ` Sam Ravnborg
2008-12-02 6:24 Stephen Rothwell
2008-12-02 11:22 ` Rusty Russell
2008-12-04 0:04 ` David Miller
2008-11-30 23:46 Stephen Rothwell
2008-12-01 5:41 ` Sam Ravnborg
2008-12-01 7:23 ` David Miller
2008-07-28 6:38 Stephen Rothwell
2008-07-28 8:21 ` Sam Ravnborg
2008-07-28 9:31 ` Adrian Bunk
2008-07-28 15:12 ` Stephen Rothwell
2008-07-28 10:12 ` Stephen Rothwell
2008-07-28 11:16 ` Sam Ravnborg
2008-07-25 7:05 Stephen Rothwell
2008-07-25 7:09 ` Stephen Rothwell
2008-07-26 9:25 ` David Miller
2008-08-04 4:26 ` David Miller
2008-08-04 5:35 ` Stephen Rothwell
2008-07-22 7:41 Stephen Rothwell
2008-07-22 22:47 ` David Miller
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=20090409151722.c8eabb56.sfr@canb.auug.org.au \
--to=sfr@canb$(echo .)auug.org.au \
--cc=davem@davemloft$(echo .)net \
--cc=dvhltc@us$(echo .)ibm.com \
--cc=hpa@zytor$(echo .)com \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=mingo@elte$(echo .)hu \
--cc=tglx@linutronix$(echo .)de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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