From: Olaf Hering <olh@suse.de>
To: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
vgoyal@in.ibm.com, Andrew Morton <akpm@osdl.org>
Subject: [PATCH] remove remaining crash_notes variable from arch/powerpc/kernel/machine_kexec.c
Date: Tue, 10 Jan 2006 22:31:53 +0100 [thread overview]
Message-ID: <20060110213153.GA22460@suse.de> (raw)
In-Reply-To: <200601101728.k0AHS4On018397@hera.kernel.org>
On Tue, Jan 10, Linux Kernel Mailing List wrote:
> tree e1847f5547a7a426214e9ef0719eab908ee305d7
> parent 82409411571ad89d271dc46f7fa26149fad9efdf
> author Vivek Goyal <vgoyal@in.ibm.com> Tue, 10 Jan 2006 12:51:41 -0800
> committer Linus Torvalds <torvalds@g5.osdl.org> Wed, 11 Jan 2006 00:01:26 -0800
>
> [PATCH] kdump: dynamic per cpu allocation of memory for saving cpu registers
remove remaining crash_notes definition to fix compile error
/dev/shm/linux-2.6/arch/powerpc/kernel/machine_kexec.c:21: error: conflicting types for `crash_notes'
/dev/shm/linux-2.6/include/linux/kexec.h:129: error: previous declaration of `crash_notes'
Signed-off-by: Olaf Hering <olh@suse.de>
arch/powerpc/kernel/machine_kexec.c | 6 ------
1 files changed, 6 deletions(-)
Index: linux-2.6/arch/powerpc/kernel/machine_kexec.c
===================================================================
--- linux-2.6.orig/arch/powerpc/kernel/machine_kexec.c
+++ linux-2.6/arch/powerpc/kernel/machine_kexec.c
@@ -14,12 +14,6 @@
#include <linux/threads.h>
#include <asm/machdep.h>
-/*
- * Provide a dummy crash_notes definition until crash dump is implemented.
- * This prevents breakage of crash_notes attribute in kernel/ksysfs.c.
- */
-note_buf_t crash_notes[NR_CPUS];
-
void machine_crash_shutdown(struct pt_regs *regs)
{
if (ppc_md.machine_crash_shutdown)
--
short story of a lazy sysadmin:
alias appserv=wotan
parent reply other threads:[~2006-01-10 21:31 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <200601101728.k0AHS4On018397@hera.kernel.org>]
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=20060110213153.GA22460@suse.de \
--to=olh@suse.de \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=vgoyal@in.ibm.com \
/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.