From: Ingo Molnar <mingo@elte.hu>
To: Len Brown <lenb@kernel.org>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
linux-next@vger.kernel.org, Bob Moore <robert.moore@intel.com>,
Yinghai Lu <yhlu.kernel@gmail.com>
Subject: Re: linux-next: manual merge of the acpi tree
Date: Wed, 25 Jun 2008 21:57:54 +0200 [thread overview]
Message-ID: <20080625195754.GA21689@elte.hu> (raw)
In-Reply-To: <alpine.LFD.1.10.0806251516460.3014@localhost.localdomain>
* Len Brown <lenb@kernel.org> wrote:
>
>
> On Wed, 25 Jun 2008, Ingo Molnar wrote:
>
> >
> > * Stephen Rothwell <sfr@canb.auug.org.au> wrote:
> >
> > > On Wed, 25 Jun 2008 09:15:08 +0200 Ingo Molnar <mingo@elte.hu> wrote:
> > > >
> > > > I suspect we cannot really eliminate this particular conflict
> > > > because the latter change is a (much welcome!) infrastructure
> > > > cleanup in all things ACPI, the former is an early init
> > > > refactoring/cleanup that depends on a whole lot of other (non-ACPI)
> > > > changes in tip/x86/*. It's too late in .26-rc cycle to push the
> > > > infrastructure cleanup upstream, so i suspect we have to live with
> > > > this conflict for a while.
> > >
> > > No problem. How long can it be until all this is merged in Linus'
> > > tree anyway? :-)
> >
> > if Len acks these patches i can do a by-line mini-topic with just these
> > commits and put them into tip/auto-x86-next. It's Len's call though :-)
>
> Ingo,
> can you point me tot he patches you'd like me to review/ack?
>
> I don't understand how you propose to void a linux-next merge conflict
> -- unless you're going to cherry-pick the ACPICA changes into your
> tree?
sorry, i was thinking about a different issue - you are right that in
this case there's little we can do.
I was thinking about these:
acpi-acpi_numa_init-build-fix
ia64, acpi: fix Altix boot breakage in ACPI
acpi: fix boot breakage on Altix
note that this build failure does _not_ occur with current mainline, so
it's a linux-next issue.
i've prepared a tip/acpi-for-len branch for you so that you can have a
look at these, you can pull them from:
git://git.kernel.org/pub/scm/linux/kernel/git/tip/linux-2.6-tip.git acpi-for-len
Thanks,
Ingo
------------------>
Ingo Molnar (1):
acpi: NR_NODE_MEMBLKS build fix
Russ Anderson (2):
ia64, acpi: fix Altix boot breakage in ACPI
acpi: fix boot breakage on Altix, #2
arch/ia64/Kconfig | 4 ++++
drivers/acpi/numa.c | 4 ++++
include/linux/acpi.h | 2 +-
3 files changed, 9 insertions(+), 1 deletions(-)
diff --git a/arch/ia64/Kconfig b/arch/ia64/Kconfig
index 16be414..1be94eb 100644
--- a/arch/ia64/Kconfig
+++ b/arch/ia64/Kconfig
@@ -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
diff --git a/drivers/acpi/numa.c b/drivers/acpi/numa.c
index 658e5f3..0fb4d2a 100644
--- a/drivers/acpi/numa.c
+++ b/drivers/acpi/numa.c
@@ -199,6 +199,7 @@ acpi_parse_processor_affinity(struct acpi_subtable_header * header,
return 0;
}
+#ifdef CONFIG_HAVE_ARCH_PARSE_SRAT
static int __init
acpi_parse_memory_affinity(struct acpi_subtable_header * header,
const unsigned long end)
@@ -216,6 +217,7 @@ acpi_parse_memory_affinity(struct acpi_subtable_header * header,
return 0;
}
+#endif
static int __init acpi_parse_srat(struct acpi_table_header *table)
{
@@ -244,9 +246,11 @@ int __init acpi_numa_init(void)
if (!acpi_table_parse(ACPI_SIG_SRAT, acpi_parse_srat)) {
acpi_table_parse_srat(ACPI_SRAT_TYPE_CPU_AFFINITY,
acpi_parse_processor_affinity, NR_CPUS);
+#ifdef CONFIG_HAVE_ARCH_PARSE_SRAT
acpi_table_parse_srat(ACPI_SRAT_TYPE_MEMORY_AFFINITY,
acpi_parse_memory_affinity,
NR_NODE_MEMBLKS);
+#endif
}
/* SLIT: System Locality Information Table */
diff --git a/include/linux/acpi.h b/include/linux/acpi.h
index 41f7ce7..b426ac5 100644
--- a/include/linux/acpi.h
+++ b/include/linux/acpi.h
@@ -93,7 +93,7 @@ int acpi_parse_mcfg (struct acpi_table_header *header);
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)
next prev parent reply other threads:[~2008-06-25 19:58 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-25 4:20 linux-next: manual merge of the acpi tree Stephen Rothwell
2008-06-25 7:15 ` Ingo Molnar
2008-06-25 15:59 ` Stephen Rothwell
2008-06-25 16:29 ` Ingo Molnar
2008-06-25 19:18 ` Len Brown
2008-06-25 19:57 ` Ingo Molnar [this message]
2008-06-26 22:42 ` Len Brown
2008-06-27 7:17 ` Ingo Molnar
2008-06-25 14:24 ` Stephen Rothwell
-- strict thread matches above, loose matches on Subject: below --
2008-12-01 2:10 Stephen Rothwell
2008-12-01 2:55 ` Len Brown
2008-12-01 3:02 ` Stephen Rothwell
2008-12-01 4:11 ` Len Brown
2008-12-01 4:37 ` Stephen Rothwell
2008-10-21 2:55 Stephen Rothwell
2008-10-20 4:45 Stephen Rothwell
2008-10-15 4:23 Stephen Rothwell
2008-10-15 16:10 ` Bjorn Helgaas
2008-10-15 4:14 Stephen Rothwell
2008-08-25 5:48 Stephen Rothwell
2008-07-17 4:22 Stephen Rothwell
2008-07-17 7:24 ` Adrian Bunk
2008-07-18 0:37 ` Stephen Rothwell
2008-07-17 4:05 Stephen Rothwell
2008-07-17 4:00 Stephen Rothwell
2008-07-17 4:29 ` Stephen Rothwell
2008-07-16 5:33 Stephen Rothwell
2008-07-16 5:35 ` Harvey Harrison
2008-07-09 3:13 Stephen Rothwell
2008-07-08 3:03 Stephen Rothwell
2008-07-08 8:18 ` Stephen Rothwell
2008-07-08 2:59 Stephen Rothwell
2008-07-08 14:33 ` Rafael J. Wysocki
2008-06-30 5:59 Stephen Rothwell
2008-06-30 6:09 ` Stephen Rothwell
2008-06-30 9:03 ` Ingo Molnar
2008-06-27 3:14 Stephen Rothwell
2008-06-26 4:21 Stephen Rothwell
2008-06-25 4:13 Stephen Rothwell
2008-06-23 4:19 Stephen Rothwell
2008-06-23 21:56 ` Ingo Molnar
2008-06-16 4:03 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=20080625195754.GA21689@elte.hu \
--to=mingo@elte.hu \
--cc=lenb@kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=robert.moore@intel.com \
--cc=sfr@canb.auug.org.au \
--cc=yhlu.kernel@gmail.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 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).