public inbox for linux-next@vger.kernel.org 
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@elte•hu>
To: Stephen Rothwell <sfr@canb•auug.org.au>
Cc: Thomas Gleixner <tglx@linutronix•de>,
	"H. Peter Anvin" <hpa@zytor•com>,
	linux-next@vger•kernel.org
Subject: Re: linux-next: x86 tree build failure
Date: Tue, 17 Jun 2008 08:08:35 +0200	[thread overview]
Message-ID: <20080617060835.GA16162@elte.hu> (raw)
In-Reply-To: <20080617055816.GA13556@elte.hu>


* Ingo Molnar <mingo@elte•hu> wrote:

> > NR_NODE_MEMBLKS is defined in linux/acpi.h if 
> > CONFIG_HAVE_ARCH_PARSE_SRAT is defined and in asm-x86/acpi.h if 
> > CONFIG_ACPI_NUMA and CONFIG_X86_64 are defined ...
> 
> that's not really the x86 tree's fault, i've been carrying the fix for 
> that problem in tip/out-of-tree for 1.5 months:
> 
> | commit d94325315f241f86bd07a2ce113cbf28dc98de72
> | Author: Ingo Molnar <mingo@elte•hu>
> | Date:   Thu May 1 09:51:47 2008 +0000
> |
> |     acpi-acpi_numa_init-build-fix
> |
> |     x86.git testing found the following build error on latest -git:
> |
> |     drivers/acpi/numa.c: In function 'acpi_numa_init':
> |     drivers/acpi/numa.c:226: error: 'NR_NODE_MEMBLKS' undeclared (first use in
> |     drivers/acpi/numa.c:226: error: (Each undeclared identifier is reported onl
> |     drivers/acpi/numa.c:226: error: for each function it appears in.)

note, if you cherry-pick that, you'll also need:

| commit aca9de453911d095a9701ee6ebbae7fd3d6c7c1e
| Author: Russ Anderson <rja@sgi•com>
| Date:   Fri May 16 10:02:06 2008 -0500
|
|     acpi: fix boot breakage on Altix

	Ingo

  reply	other threads:[~2008-06-17  6:08 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-06-17  3:46 linux-next: x86 tree build failure Stephen Rothwell
2008-06-17  5:58 ` Ingo Molnar
2008-06-17  6:08   ` Ingo Molnar [this message]
2008-06-17  6:45     ` Ingo Molnar
2008-06-18  5:04   ` Stephen Rothwell
2008-06-18  6:39     ` Ingo Molnar
2008-06-25  3:17 ` Stephen Rothwell
  -- strict thread matches above, loose matches on Subject: below --
2008-07-17  2:07 Stephen Rothwell
2008-07-17  9:23 ` Vegard Nossum
2008-07-18 20:10   ` Ingo Molnar
2008-07-18 20:12     ` Ingo Molnar
2008-07-19 12:11       ` Stephen Rothwell
2008-08-25 10:22 Stephen Rothwell
2008-08-25 10:28 ` Ingo Molnar
2008-09-11 23:56 Stephen Rothwell
2008-09-12  6:05 ` Joerg Roedel
2008-09-12  7:31   ` Stephen Rothwell
2008-09-12  7:54     ` Joerg Roedel
2008-09-12  8:30     ` Ingo Molnar
2008-09-14 19:52       ` Stephen Rothwell

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=20080617060835.GA16162@elte.hu \
    --to=mingo@elte$(echo .)hu \
    --cc=hpa@zytor$(echo .)com \
    --cc=linux-next@vger$(echo .)kernel.org \
    --cc=sfr@canb$(echo .)auug.org.au \
    --cc=tglx@linutronix$(echo .)de \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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