[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <87fvf73c6g.fsf@intel.com>
Date: Wed, 01 Oct 2014 20:57:43 +0300
From: Jani Nikula <jani.nikula@...ux.intel.com>
To: Jim Davis <jim.epost@...il.com>,
Stephen Rothwell <sfr@...b.auug.org.au>,
linux-next <linux-next@...r.kernel.org>,
linux-kernel <linux-kernel@...r.kernel.org>,
David Airlie <airlied@...ux.ie>, daniel.vetter@...el.com,
intel-gfx@...ts.freedesktop.org,
dri-devel <dri-devel@...ts.freedesktop.org>
Subject: Re: randconfig build error with next-20141001, in drivers/gpu/drm/i915
On Wed, 01 Oct 2014, Jim Davis <jim.epost@...il.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).
BR,
Jani.
--
Jani Nikula, Intel Open Source Technology Center
--
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