From: Takashi Iwai Subject: Bad rever-select of CONFIG_SND_HDA_I915 Date: Fri, 18 Mar 2016 08:34:49 +0100 Message-ID: Mime-Version: 1.0 (generated by SEMI 1.14.6 - "Maruoka") Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: Received: from mx2.suse.de (mx2.suse.de [195.135.220.15]) by alsa0.perex.cz (Postfix) with ESMTP id 99EDD261293 for ; Fri, 18 Mar 2016 08:34:51 +0100 (CET) List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: alsa-devel-bounces@alsa-project.org Sender: alsa-devel-bounces@alsa-project.org To: Vinod Koul Cc: Liam Girdwood , alsa-devel@alsa-project.org, Mark Brown List-Id: alsa-devel@alsa-project.org Hi, while build testing, I noticed the following warning: warning: (SND_SOC_INTEL_SKYLAKE) selects SND_HDA_I915 which has unmet direct dependencies (SOUND && !M68K && !UML && SND && DRM_I915 && SND_HDA_CORE) And it's indeed broken: you can't select CONFIG_SND_HDA_I915 from the driver side. This is the condition depending on DRM i915 driver. Fixing this doesn't look too trivial, though. Since SND_SOC_INTEL_SKYLAKE is the item to be selected, it can't have "depends on". So, the top-level configs that select SND_SOC_INTEL_SKYLAKE need to have "depends on DRM_I915" lines, or modify the driver to be built without i915 binding. Takashi