From: Len Brown <lenb@kernel.org>
To: Randy Dunlap <randy.dunlap@oracle.com>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
linux-acpi@vger.kernel.org, linux-next@vger.kernel.org,
LKML <linux-kernel@vger.kernel.org>,
Lee@kernel.org, Chun-Yi <joeyli.kernel@gmail.com>,
Dave Airlie <airlied@redhat.com>, Zhang Rui <rui.zhang@intel.com>
Subject: Re: linux-next: Tree for October 28 (acpi_video)
Date: Fri, 29 Oct 2010 14:18:04 -0400 (EDT) [thread overview]
Message-ID: <alpine.LFD.2.00.1010291406560.3423@localhost.localdomain> (raw)
In-Reply-To: <20101029090131.68709a71.randy.dunlap@oracle.com>
> drivers/built-in.o: In function `acpi_video_bus_put_one_device':
> video.c:(.text+0x9d794): undefined reference to `backlight_device_unregister'
Invalid .config, as ACPI_VIDEO depends on BACKLIGHT_CLASS_DEVICE, which is not set.
This breakage is the infamous "select in Kconfig doesn't" bug,
which has apparently claimed a new victim, STUB_POULSBO:
(STUB_POULSBO && HAS_IOMEM && PCI && ACPI || DRM_I915 && <choice> &&
AGP_INTEL && ACPI || DRM_NOUVEAU && STAGING && !STAGING_EXCLUDE_BUILD &&
DRM && PCI && ACPI) selects ACPI_VIDEO which has unmet direct dependencies
(ACPI && X86 && BACKLIGHT_CLASS_DEVICE && VIDEO_OUTPUT_CONTROL && INPUT)
commit e26fd1199ebab0d469fc3e037da5932d382f0669
Author: Lee, Chun-Yi <joeyli.kernel@gmail.com>
Date: Wed Oct 20 13:51:19 2010 +0800
gpu: Add Intel GMA500(Poulsbo) Stub Driver
Currently, there have no GMA500(Poulsbo) native video driver to
support
intel opregion. So, use this stub driver to enable the acpi backlight
control sysfs entry files by requrest acpi_video_register.
[airlied: fix warnings]
Signed-off-by: Lee, Chun-Yi <jlee@novell.com>
Signed-off-by: Dave Airlie <airlied@redhat.com>
next prev parent reply other threads:[~2010-10-29 18:18 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-28 3:20 linux-next: Tree for October 28 Stephen Rothwell
2010-10-29 16:01 ` linux-next: Tree for October 28 (acpi_video) Randy Dunlap
2010-10-29 18:18 ` Len Brown [this message]
2010-11-01 3:09 ` Randy Dunlap
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.2.00.1010291406560.3423@localhost.localdomain \
--to=lenb@kernel.org \
--cc=Lee@kernel.org \
--cc=airlied@redhat.com \
--cc=joeyli.kernel@gmail.com \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=randy.dunlap@oracle.com \
--cc=rui.zhang@intel.com \
--cc=sfr@canb.auug.org.au \
/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