[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20080216214410.b9699910.akpm@linux-foundation.org>
Date: Sat, 16 Feb 2008 21:44:10 -0800
From: Andrew Morton <akpm@...ux-foundation.org>
To: Randy Dunlap <randy.dunlap@...cle.com>
Cc: linux-kernel@...r.kernel.org, len.brown@...el.com,
linux-acpi@...r.kernel.org,
Thomas Petazzoni <thomas.petazzoni@...e-electrons.com>
Subject: Re: 2.6.25-rc2-mm1 (x64 thermal build failure)
On Sat, 16 Feb 2008 21:16:03 -0800 Randy Dunlap <randy.dunlap@...cle.com> wrote:
> On Sat, 16 Feb 2008 00:25:22 -0800 Andrew Morton wrote:
>
> >
> > ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.25-rc2/2.6.25-rc2-mm1/
>
> ACPI is enabled, but DMI=n.
>
> linux-2.6.25-rc2-mm1/drivers/acpi/thermal.c: In function 'acpi_thermal_init':
> linux-2.6.25-rc2-mm1/drivers/acpi/thermal.c:1792: error: 'thermal_dmi_table' undeclared (first use in this function)
> linux-2.6.25-rc2-mm1/drivers/acpi/thermal.c:1792: error: (Each undeclared identifier is reported only once
> linux-2.6.25-rc2-mm1/drivers/acpi/thermal.c:1792: error: for each function it appears in.)
> make[3]: *** [drivers/acpi/thermal.o] Error 1
>
Bustage in x86-configurable-dmi-scanning-code.patch. Previously, DMI=y was
just hardwired. Now, it becomes selectable and stuff breaks.
I guess the DMI=n version of dmi_check_system() could become a macro so we
don't emit a reference to its argument, but that might generate
unused-variable warnings elsewhere.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists