From: David Brownell <david-b@pacbell.net>
To: linux-pm@lists.linux-foundation.org
Cc: Ingo Molnar <mingo@elte.hu>, Len Brown <lenb@kernel.org>,
linux-acpi@vger.kernel.org,
Andrew Morton <akpm@linux-foundation.org>,
Linus Torvalds <torvalds@linux-foundation.org>,
linux-kernel@vger.kernel.org
Subject: Re: [linux-pm] [patch] acpi: fix drivers/acpi/glue.c build error
Date: Wed, 30 Apr 2008 15:17:55 -0700 [thread overview]
Message-ID: <200804301517.56249.david-b@pacbell.net> (raw)
In-Reply-To: <20080430210026.GA24121@elte.hu>
On Wednesday 30 April 2008, Ingo Molnar wrote:
> Subject: acpi: fix drivers/acpi/glue.c build error
> From: Ingo Molnar <mingo@elte.hu>
> Date: Wed Apr 30 22:56:57 CEST 2008
>
> 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.
Broken config, yes? ACPI selects PNP ...
--
To unsubscribe from this list: send the line "unsubscribe linux-acpi" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
WARNING: multiple messages have this Message-ID (diff)
From: David Brownell <david-b@pacbell.net>
To: linux-pm@lists.linux-foundation.org
Cc: Ingo Molnar <mingo@elte.hu>, Len Brown <lenb@kernel.org>,
linux-acpi@vger.kernel.org,
Andrew Morton <akpm@linux-foundation.org>,
Linus Torvalds <torvalds@linux-foundation.org>,
linux-kernel@vger.kernel.org
Subject: Re: [linux-pm] [patch] acpi: fix drivers/acpi/glue.c build error
Date: Wed, 30 Apr 2008 15:17:55 -0700 [thread overview]
Message-ID: <200804301517.56249.david-b@pacbell.net> (raw)
In-Reply-To: <20080430210026.GA24121@elte.hu>
On Wednesday 30 April 2008, Ingo Molnar wrote:
> Subject: acpi: fix drivers/acpi/glue.c build error
> From: Ingo Molnar <mingo@elte.hu>
> Date: Wed Apr 30 22:56:57 CEST 2008
>
> 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.
Broken config, yes? ACPI selects PNP ...
next prev parent reply other threads:[~2008-04-30 22:17 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-30 18:20 [GIT PATCH] ACPI patches for 2.6.26-rc0 Len Brown
2008-04-30 18:43 ` Andrew Morton
2008-04-30 18:43 ` Andrew Morton
2008-04-30 19:00 ` Rafael J. Wysocki
2008-04-30 19:00 ` Rafael J. Wysocki
2008-04-30 18:55 ` Linus Torvalds
2008-05-01 0:26 ` Stephen Rothwell
2008-05-01 12:16 ` Adrian Bunk
2008-05-01 12:16 ` Adrian Bunk
2008-05-01 0:26 ` Stephen Rothwell
2008-05-01 6:39 ` Len Brown
2008-05-01 6:39 ` Len Brown
2008-04-30 18:55 ` Linus Torvalds
2008-04-30 20:56 ` [patch] acpi: acpi_numa_init() build fix Ingo Molnar
2008-04-30 21:00 ` [patch] acpi: fix drivers/acpi/glue.c build error Ingo Molnar
2008-04-30 21:00 ` Ingo Molnar
2008-04-30 22:17 ` David Brownell [this message]
2008-04-30 22:17 ` [linux-pm] " David Brownell
2008-04-30 22:17 ` David Brownell
2008-04-30 20:56 ` [patch] acpi: acpi_numa_init() build fix 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=200804301517.56249.david-b@pacbell.net \
--to=david-b@pacbell.net \
--cc=akpm@linux-foundation.org \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@lists.linux-foundation.org \
--cc=mingo@elte.hu \
--cc=torvalds@linux-foundation.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.