Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1031439AbbDXRHv (ORCPT ); Fri, 24 Apr 2015 13:07:51 -0400 Received: from mga01.intel.com ([192.55.52.88]:18448 "EHLO mga01.intel.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1030732AbbDXRHu (ORCPT ); Fri, 24 Apr 2015 13:07:50 -0400 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.11,641,1422950400"; d="scan'208";a="715093781" From: Jani Nikula To: Jim Davis , Stephen Rothwell , linux-next , linux-kernel , daniel.vetter@intel.com, David Airlie , dri-devel , intel-gfx@lists.freedesktop.org Subject: Re: randconfig build error with next-20150424, in drivers/gpu/drm/i915 In-Reply-To: Organization: Intel Finland Oy - BIC 0357606-4 - Westendinkatu 7, 02160 Espoo References: User-Agent: Notmuch/0.19+87~gcf99a78 (http://notmuchmail.org) Emacs/24.4.1 (x86_64-pc-linux-gnu) Date: Fri, 24 Apr 2015 20:09:32 +0300 Message-ID: <87wq11bghf.fsf@intel.com> MIME-Version: 1.0 Content-Type: text/plain Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1594 Lines: 41 On Fri, 24 Apr 2015, Jim Davis 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 -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/