From: Adrian Bunk <bunk@stusta.de>
To: Kirill Korotaev <dev@sw.ru>, Pavel Emelianov <xemul@sw.ru>
Cc: Andrew Morton <akpm@osdl.org>,
James.Bottomley@HansenPartnership.com,
linux-kernel@vger.kernel.org
Subject: -mm: sysrq patch breaks Voyager build
Date: Fri, 17 Mar 2006 13:38:49 +0100 [thread overview]
Message-ID: <20060317123849.GI3914@stusta.de> (raw)
nmi-lockup-and-altsysrq-p-dumping-calltraces-on-_all_-cpus.patch causes
the following compile error with CONFIG_X86_VOYAGER=y:
<-- snip -->
...
LD .tmp_vmlinux1
arch/i386/kernel/built-in.o: In function `die_nmi': undefined reference to `smp_show_regs'
arch/i386/kernel/built-in.o: In function `die_nmi': undefined reference to `smp_nmi_call_function'
drivers/built-in.o: In function `sysrq_handle_showregs':sysrq.c:(.text+0x255ef): undefined reference to `smp_show_regs'
:sysrq.c:(.text+0x255f4): undefined reference to `smp_nmi_call_function'
make: *** [.tmp_vmlinux1] Error 1
<-- snip -->
cu
Adrian
--
"Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
"Only a promise," Lao Er said.
Pearl S. Buck - Dragon Seed
reply other threads:[~2006-03-17 12:38 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=20060317123849.GI3914@stusta.de \
--to=bunk@stusta.de \
--cc=James.Bottomley@HansenPartnership.com \
--cc=akpm@osdl.org \
--cc=dev@sw.ru \
--cc=linux-kernel@vger.kernel.org \
--cc=xemul@sw.ru \
/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