From: Len Brown <lenb@kernel.org>
To: akpm@linux-foundation.org
Cc: linux-acpi@vger.kernel.org, mingo@elte.hu, bjorn.helgaas@hp.com
Subject: Re: [patch (for 2.6.26?) 2/2] acpi: fix drivers/acpi/glue.c build error
Date: Tue, 10 Jun 2008 12:14:08 -0400 (EDT) [thread overview]
Message-ID: <alpine.LFD.1.10.0806101212360.14381@localhost.localdomain> (raw)
In-Reply-To: <200806092348.m59NmJnC015625@imap1.linux-foundation.org>
On Mon, 9 Jun 2008, akpm@linux-foundation.org wrote:
> From: Ingo Molnar <mingo@elte.hu>
>
> x86.git testing found the following build bug:
>
> drivers/built-in.o: In function `acpi_rtc_init':
> glue.c:(.init.text+0x16c3): undefined reference to `pnp_bus_type'
>
> this tries to use PNP bus infrastructure even in the !PNP case.
>
> Signed-off-by: Ingo Molnar <mingo@elte.hu>
> Cc: Bjorn Helgaas <bjorn.helgaas@hp.com>
> Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
> ---
>
> drivers/acpi/glue.c | 3 +++
> 1 file changed, 3 insertions(+)
>
> diff -puN drivers/acpi/glue.c~acpi-fix-drivers-acpi-gluec-build-error drivers/acpi/glue.c
> --- a/drivers/acpi/glue.c~acpi-fix-drivers-acpi-gluec-build-error
> +++ a/drivers/acpi/glue.c
> @@ -303,6 +303,7 @@ static void rtc_wake_off(struct device *
>
> static struct cmos_rtc_board_info rtc_info;
>
> +#ifdef CONFIG_PNP
>
> /* PNP devices are registered in a subsys_initcall();
> * ACPI specifies the PNP IDs to use.
> @@ -364,4 +365,6 @@ static int __init acpi_rtc_init(void)
> /* do this between RTC subsys_initcall() and rtc_cmos driver_initcall() */
> fs_initcall(acpi_rtc_init);
>
> +#endif /* CONFIG_PNP */
> +
> #endif
ENOREPRODUCE
I'm unable to convince "make oldconfig" to allow a
CONFIG_ACPI=y CONFIG_PNP=n build.
-Len
next prev parent reply other threads:[~2008-06-10 16:20 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-09 23:48 [patch (for 2.6.26?) 2/2] acpi: fix drivers/acpi/glue.c build error akpm
2008-06-10 16:14 ` Len Brown [this message]
2008-06-10 21:00 ` Andrew Morton
2008-06-12 12:19 ` Ingo Molnar
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=alpine.LFD.1.10.0806101212360.14381@localhost.localdomain \
--to=lenb@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=bjorn.helgaas@hp.com \
--cc=linux-acpi@vger.kernel.org \
--cc=mingo@elte.hu \
/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