From: Jani Nikula <jani.nikula@linux.intel.com>
To: 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>,
daniel.vetter@intel.com, David Airlie <airlied@linux.ie>,
dri-devel <dri-devel@lists.freedesktop.org>,
intel-gfx@lists.freedesktop.org
Subject: Re: randconfig build error with next-20150424, in drivers/gpu/drm/i915
Date: Fri, 24 Apr 2015 20:09:32 +0300 [thread overview]
Message-ID: <87wq11bghf.fsf@intel.com> (raw)
In-Reply-To: <CA+r1ZhjaK_cpPa2bS-VdJxExPfsC42J1zb1WoxnR48O6OFPVXg@mail.gmail.com>
On Fri, 24 Apr 2015, Jim Davis <jim.epost@gmail.com> wrote:
> Building with the attached random configuration file,
>
> warning: (SND_SOC_INTEL_BYTCR_RT5640_MACH &&
> SND_SOC_INTEL_CHT_BSW_RT5672_MACH &&
> SND_SOC_INTEL_CHT_BSW_RT5645_MACH) selects SND_SST_IPC_ACPI which has
> unmet direct dependencies (SOUND && !M68K && !UML && SND && SND_SOC &&
> ACPI)
>
> drivers/built-in.o: In function `intel_backlight_register':
> (.text+0xfaafa): undefined reference to `backlight_device_register'
> drivers/built-in.o: In function `intel_backlight_unregister':
> (.text+0xfab7d): undefined reference to `backlight_device_unregister'
This is because you end up with:
CONFIG_DRM_I915=y
CONFIG_BACKLIGHT_CLASS_DEVICE=m
which is due to i915 selecting, not depending on, backlight class
device. But we can't just switch to depend in i915, because it creates
circular dependencies across the board, and to fix that we end up with a
patch I proposed about six months ago [1]. See the discussion there, and
also [2]. I think switching from select to depend on is the technically
right fix, but I don't have the time to fight this across all affected
subsystems.
BR,
Jani.
[1] http://mid.gmane.org/1413580403-16225-1-git-send-email-jani.nikula@intel.com
[2] http://mid.gmane.org/87wq1wot9b.fsf@intel.com
--
Jani Nikula, Intel Open Source Technology Center
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel
prev parent reply other threads:[~2015-04-24 17:09 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-24 16:36 randconfig build error with next-20150424, in drivers/gpu/drm/i915 Jim Davis
2015-04-24 17:09 ` Jani Nikula [this message]
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=87wq11bghf.fsf@intel.com \
--to=jani.nikula@linux.intel.com \
--cc=airlied@linux.ie \
--cc=daniel.vetter@intel.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox