Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751859AbXB1Tpa (ORCPT ); Wed, 28 Feb 2007 14:45:30 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1751853AbXB1Tp3 (ORCPT ); Wed, 28 Feb 2007 14:45:29 -0500 Received: from netops-testserver-4-out.sgi.com ([192.48.171.29]:60377 "EHLO netops-testserver-4.corp.sgi.com" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1751806AbXB1TpS (ORCPT ); Wed, 28 Feb 2007 14:45:18 -0500 From: John Keller To: fastboot@lists.osdl.org Cc: jlan@sgi.com, linux-ia64@vger.kernel.org, linux-kernel@vger.kernel.org, John Keller Date: Wed, 28 Feb 2007 13:45:17 -0600 Message-Id: <20070228194517.25635.98535.sendpatchset@attica.americas.sgi.com> Subject: [PATCH 1/1] - platform_kernel_launch_event is noop on generic kernel Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1185 Lines: 25 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 --- 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 - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/