From: Pierre-Louis Bossart <pierre-louis.bossart@linux.intel.com>
To: Randy Dunlap <rdunlap@infradead.org>,
Stephen Rothwell <sfr@canb.auug.org.au>,
Linux Next Mailing List <linux-next@vger.kernel.org>
Cc: Liam Girdwood <liam.r.girdwood@linux.intel.com>,
moderated for non-subscribers <alsa-devel@alsa-project.org>,
Jie Yang <yang.jie@linux.intel.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [alsa-devel] linux-next: Tree for Dec 21 (SND_HDA_INTEL_DSP_DETECTION)
Date: Fri, 21 Dec 2018 14:39:11 -0600 [thread overview]
Message-ID: <ff6289e5-64c8-5787-0556-4e339205b5f6@linux.intel.com> (raw)
In-Reply-To: <4d04710b-d661-fea7-2542-8e9c46f59173@infradead.org>
On 12/21/18 12:02 PM, Randy Dunlap wrote:
> On 12/21/18 12:32 AM, Stephen Rothwell wrote:
>> Hi all,
>>
>> News: there will be no linux-next release until Jan 2. Have a good break.
>>
>> Changes since 20181220:
>>
> on x86_64:
>
> A new group of Kconfig "select"s is causing kconfig warnings:
>
> WARNING: unmet direct dependencies detected for SND_HDA_INTEL_DSP_DETECTION_CFL
> Depends on [n]: SOUND [=y] && !UML && SND [=y] && SND_HDA [=n] && SND_HDA_INTEL [=n]
> Selected by [y]:
> - SND_SOC_INTEL_SKYLAKE_COMMON [=y] && SOUND [=y] && !UML && SND [=y] && SND_SOC [=y] && SND_SOC_INTEL_SST_TOPLEVEL [=y] && SND_SOC_INTEL_SKYLAKE_FAMILY [=y] && SND_SOC_INTEL_CFL [=y]
Ack, thanks for the report. This shouldn't have any functional impact
but we can easily remove the warnings. will send a patch shortly.
-Pierre
next prev parent reply other threads:[~2018-12-21 20:39 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-21 8:32 linux-next: Tree for Dec 21 Stephen Rothwell
2018-12-21 16:21 ` Guenter Roeck
2018-12-21 16:33 ` Ard Biesheuvel
2018-12-21 20:57 ` Florian Westphal
2018-12-22 6:43 ` Chandan Rajendra
2018-12-24 8:20 ` Greg Kroah-Hartman
2018-12-31 14:01 ` Vinod Koul
2018-12-21 16:37 ` linux-next: Tree for Dec 21 (acpi without CONFIG_PCI) Randy Dunlap
[not found] ` <CAK9iUCO_Pk3eYH+hyMuqU6weDsbzC9Sg1Z719fm8u_3Oh7s-iQ@mail.gmail.com>
2018-12-21 17:26 ` Randy Dunlap
2018-12-21 17:43 ` Randy Dunlap
2018-12-22 0:05 ` Sinan Kaya
2018-12-21 18:28 ` Randy Dunlap
2018-12-22 0:04 ` Sinan Kaya
2018-12-21 17:08 ` linux-next: Tree for Dec 21 (nvdimm/security.o) Randy Dunlap
2018-12-21 18:51 ` Dan Williams
2018-12-21 21:01 ` Dan Williams
2018-12-21 17:35 ` linux-next: Tree for Dec 21 (mmc/host/sdhci-omap.c) Randy Dunlap
2018-12-21 18:02 ` linux-next: Tree for Dec 21 (SND_HDA_INTEL_DSP_DETECTION) Randy Dunlap
2018-12-21 20:39 ` Pierre-Louis Bossart [this message]
2018-12-21 18:36 ` linux-next: Tree for Dec 21 (FB_BACKLIGHT) 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=ff6289e5-64c8-5787-0556-4e339205b5f6@linux.intel.com \
--to=pierre-louis.bossart@linux.intel.com \
--cc=alsa-devel@alsa-project.org \
--cc=liam.r.girdwood@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=rdunlap@infradead.org \
--cc=sfr@canb.auug.org.au \
--cc=yang.jie@linux.intel.com \
/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;
as well as URLs for NNTP newsgroup(s).