linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Andy Whitcroft <apw@shadowen.org>
To: Andrew Morton <akpm@digeo.com>,
	"Eric W. Biederman" <ebiederm@xmission.com>
Cc: linux-kernel@vger.kernel.org, linux-mm@kvack.org
Subject: Re: 2.5.69-mm7
Date: Tue, 20 May 2003 12:52:31 -0700	[thread overview]
Message-ID: <535806509.1053435150@IBM-O1F8DZ9MWMH> (raw)
In-Reply-To: <20030519012336.44d0083a.akpm@digeo.com>

Seems that -mm7, has broken compilation of subarch visws:

arch/i386/kernel/built-in.o: In function `cpu_stop_apics':
arch/i386/kernel/built-in.o(.text+0xe511): undefined reference to 
`stop_this_cpu'
arch/i386/kernel/built-in.o: In function `stop_apics':
arch/i386/kernel/built-in.o(.text+0xe552): undefined reference to 
`reboot_cpu'
arch/i386/mach-visws/built-in.o: In function `machine_restart':
arch/i386/mach-visws/built-in.o(.text+0x1): undefined reference to 
`smp_send_stop'

Seems that the culprit is the reboot on boot processor changes, reverting 
the following patches fixes the compilation:

	patch -R -p1 <kexec-revert-NORET_TYPE.patch
	patch -R -p1 <reboot_on_bsp.patch

Cheers.

-apw
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org.  For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"aart@kvack.org"> aart@kvack.org </a>

  parent reply	other threads:[~2003-05-20 19:52 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-05-19  8:23 2.5.69-mm7 Andrew Morton
2003-05-19 10:30 ` 2.5.69-mm7 Rudmer van Dijk
2003-05-19 10:38   ` 2.5.69-mm7 William Lee Irwin III
2003-05-19 13:19     ` 2.5.69-mm7 Rudmer van Dijk
2003-05-19 10:58 ` 2.5.69-mm7 Alexander Hoogerhuis
2003-05-20 19:52 ` Andy Whitcroft [this message]
2003-05-20 20:01   ` 2.5.69-mm7 Eric W. Biederman
2003-05-21 12:13 ` 2.5.69-mm7 Ivan Kokshaysky

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=535806509.1053435150@IBM-O1F8DZ9MWMH \
    --to=apw@shadowen.org \
    --cc=akpm@digeo.com \
    --cc=ebiederm@xmission.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.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