LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: John Keller <jpk@sgi.com>
To: fastboot@lists.osdl.org
Cc: jlan@sgi.com, linux-ia64@vger.kernel.org,
	linux-kernel@vger.kernel.org, John Keller <jpk@sgi.com>
Subject: [PATCH 1/1] - platform_kernel_launch_event is noop on generic kernel
Date: Wed, 28 Feb 2007 13:45:17 -0600	[thread overview]
Message-ID: <20070228194517.25635.98535.sendpatchset@attica.americas.sgi.com> (raw)

Add a missing #define for the platform_kernel_launch_event.
Without this fix, a call to platform_kernel_launch_event()
becomes a noop on generic kernels. SN systems require this
fix to successfully kdump/kexec from certain hardware errors.

Signed-off-by: John Keller <jpk@sgi.com>
---

Index: linux-2.6/include/asm-ia64/machvec.h
===================================================================
--- linux-2.6.orig/include/asm-ia64/machvec.h	2007-02-28 08:39:45.764537727 -0600
+++ linux-2.6/include/asm-ia64/machvec.h	2007-02-28 08:40:01.254467899 -0600
@@ -168,6 +168,7 @@ extern void machvec_tlb_migrate_finish (
 #  define platform_setup_msi_irq	ia64_mv.setup_msi_irq
 #  define platform_teardown_msi_irq	ia64_mv.teardown_msi_irq
 #  define platform_pci_fixup_bus	ia64_mv.pci_fixup_bus
+#  define platform_kernel_launch_event	ia64_mv.kernel_launch_event
 # endif
 
 /* __attribute__((__aligned__(16))) is required to make size of the

             reply	other threads:[~2007-02-28 19:45 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-02-28 19:45 John Keller [this message]
2007-03-01  4:22 ` [Fastboot] [PATCH 1/1] - platform_kernel_launch_event is noop on generic kernel Horms
2007-03-01 12:57   ` Bernhard Walle
2007-03-01 13:03     ` Bernhard Walle
2007-03-06  2:40       ` Jay Lan

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=20070228194517.25635.98535.sendpatchset@attica.americas.sgi.com \
    --to=jpk@sgi.com \
    --cc=fastboot@lists.osdl.org \
    --cc=jlan@sgi.com \
    --cc=linux-ia64@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.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).