public inbox for linux-ia64@vger.kernel.org
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@linux-foundation.org>
To: linux-ia64@vger.kernel.org
Subject: Re: [patch] Fix Altix boot breakage in ACPI
Date: Sat, 17 May 2008 16:46:08 +0000	[thread overview]
Message-ID: <20080517094608.9b924dc6.akpm@linux-foundation.org> (raw)
In-Reply-To: <20080516202020.GA21250@sgi.com>

On Sat, 17 May 2008 09:10:35 -0500 Russ Anderson <rja@sgi.com> wrote:

> On Fri, May 16, 2008 at 03:40:28PM -0700, Luck, Tony wrote:
> > > A recent ACPI change (commit 5dc90c0b2d4bd0127624bab67cec159b2c6c4daf)
> > 
> > -ENOSUCHCOMMIT ... well I can't see it in Linus' tree.
> 
> Sorry, I should have added more information.
> 
> It is in Andrew's tree (2.6.26-rc2-mm1).  It has yet to make it to Linus' tree.
> 
> http://lkml.org/lkml/2008/5/14/366
> 
> The patch name is acpi-acpi_numa_init-build-fix
> http://kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.26-rc2/2.6.26-rc2-mm1/patch-list

That was dropped because it broke things.  umm...

	From: "Torsten Kaiser" <just.for.lkml@googlemail.com>
	To: "Andrew Morton" <akpm@linux-foundation.org>
	Cc: linux-kernel@vger.kernel.org
	Subject: Re: 2.6.26-rc2-mm1
	Date: 	Wed, 14 May 2008 21:12:13 +0200
	Sender: linux-kernel-owner@vger.kernel.org
	...
	But somehow the NUMAness of my system is gone.

> A recent ACPI change (commit 5dc90c0b2d4bd0127624bab67cec159b2c6c4daf)
> inadvertently broke Altix boot.  This patch allow Altix to boot.
> 
> 
> Signed-off-by: Russ Anderson <rja@sgi.com>
> Acked-by: Ingo Molnar <mingo@elte.hu>
> 
> ---
>  arch/ia64/Kconfig    |    4 ++++
>  include/linux/acpi.h |    2 +-
>  2 files changed, 5 insertions(+), 1 deletion(-)
> 
> Index: 2.6.26-rc2/arch/ia64/Kconfig
> =================================> --- 2.6.26-rc2.orig/arch/ia64/Kconfig	2008-05-16 09:36:37.285558037 -0500
> +++ 2.6.26-rc2/arch/ia64/Kconfig	2008-05-16 09:37:39.149204580 -0500
> @@ -60,6 +60,10 @@ config RWSEM_XCHGADD_ALGORITHM
>  	bool
>  	default y
>  
> +config HAVE_ARCH_PARSE_SRAT
> +	bool
> +	default y
> +
>  config ARCH_HAS_ILOG2_U32
>  	bool
>  	default n
> Index: 2.6.26-rc2/include/linux/acpi.h
> =================================> --- 2.6.26-rc2.orig/include/linux/acpi.h	2008-05-16 09:37:12.989971159 -0500
> +++ 2.6.26-rc2/include/linux/acpi.h	2008-05-16 09:50:17.082906375 -0500
> @@ -93,7 +93,7 @@ int acpi_parse_mcfg (struct acpi_table_h
>  void acpi_table_print_madt_entry (struct acpi_subtable_header *madt);
>  
>  /* the following four functions are architecture-dependent */
> -#ifdef CONFIG_HAVE_ARCH_PARSE_SRAT
> +#if defined(CONFIG_HAVE_ARCH_PARSE_SRAT) && !defined(NR_NODE_MEMBLKS)
>  #define NR_NODE_MEMBLKS MAX_NUMNODES
>  #define acpi_numa_slit_init(slit) do {} while (0)
>  #define acpi_numa_processor_affinity_init(pa) do {} while (0)

So this affects machines other than altix?

Who gets to merge this?  I'll plan on sending it in on Mondayish unless
I hear otherwise.

(I wish the changelog was more specific than "inadvertently broke".  It
should explain what the failure was).


  parent reply	other threads:[~2008-05-17 16:46 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-05-16 20:20 [patch] Fix Altix boot breakage in ACPI Russ Anderson
2008-05-16 22:40 ` Luck, Tony
2008-05-17 14:10 ` Russ Anderson
2008-05-17 16:46 ` Andrew Morton [this message]
2008-05-19  6:57 ` KOSAKI Motohiro

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=20080517094608.9b924dc6.akpm@linux-foundation.org \
    --to=akpm@linux-foundation.org \
    --cc=linux-ia64@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