From: Randy Dunlap <rdunlap@infradead.org>
To: Jani Nikula <jani.nikula@linux.intel.com>,
Jim Davis <jim.epost@gmail.com>,
Stephen Rothwell <sfr@canb.auug.org.au>,
linux-next <linux-next@vger.kernel.org>,
linux-kernel <linux-kernel@vger.kernel.org>,
David Airlie <airlied@linux.ie>,
daniel.vetter@intel.com, intel-gfx@lists.freedesktop.org,
dri-devel <dri-devel@lists.freedesktop.org>
Subject: Re: randconfig build error with next-20141001, in drivers/gpu/drm/i915
Date: Wed, 01 Oct 2014 11:23:47 -0700 [thread overview]
Message-ID: <542C46B3.2020901@infradead.org> (raw)
In-Reply-To: <87fvf73c6g.fsf@intel.com>
On 10/01/14 10:57, Jani Nikula wrote:
> On Wed, 01 Oct 2014, Jim Davis <jim.epost@gmail.com> wrote:
>> Building with the attached random configuration file,
>>
>> warning: (VIDEO_TIMBERDALE) selects TIMB_DMA which has unmet direct
>> dependencies (DMADEVICES && MFD_TIMBERDALE)
>> warning: (USB_OTG_FSM && FSL_USB2_OTG && USB_MV_OTG) selects USB_OTG
>> which has unmet direct dependencies (USB_SUPPORT && USB && PM_RUNTIME)
>>
>> drivers/built-in.o: In function `intel_panel_setup_backlight':
>> (.text+0x11855d): undefined reference to `backlight_device_register'
>> drivers/built-in.o: In function `intel_panel_destroy_backlight':
>> (.text+0x118624): undefined reference to `backlight_device_unregister'
>> make: *** [vmlinux] Error 1
>
> It's the combination:
>
>> CONFIG_DRM_I915=y
>> CONFIG_BACKLIGHT_CLASS_DEVICE=m
>
> Not sure what the Kconfig magic spell needs to be when we don't want to
> depend on CONFIG_BACKLIGHT_CLASS_DEVICE but we'll use it if it's enabled
> (y or m).
Something like:
depends on BACKLIGHT_CLASS_DEVICE || BACKLIGHT_CLASS_DEVICE=n
is what we usually use.
--
~Randy
next prev parent reply other threads:[~2014-10-01 18:23 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-01 14:48 randconfig build error with next-20141001, in drivers/gpu/drm/i915 Jim Davis
2014-10-01 17:57 ` Jani Nikula
2014-10-01 18:23 ` Randy Dunlap [this message]
2014-10-02 7:46 ` Jani Nikula
2014-10-02 16:56 ` 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=542C46B3.2020901@infradead.org \
--to=rdunlap@infradead.org \
--cc=airlied@linux.ie \
--cc=daniel.vetter@intel.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=jani.nikula@linux.intel.com \
--cc=jim.epost@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--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 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.