From: Randy Dunlap <rdunlap@infradead.org>
To: Stephen Rothwell <sfr@canb.auug.org.au>,
Linux Next Mailing List <linux-next@vger.kernel.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
moderated for non-subscribers <alsa-devel@alsa-project.org>,
Mark Brown <broonie@kernel.org>,
patches@opensource.cirrus.com
Subject: Re: linux-next: Tree for Feb 18 (sound/soc/codecs/wm5110.c)
Date: Mon, 17 Feb 2020 23:05:49 -0800 [thread overview]
Message-ID: <c2273472-18af-e206-c942-fd460e0d192c@infradead.org> (raw)
In-Reply-To: <89ef264f-12c9-ccb0-5cdd-ee5f70a469dd@infradead.org>
[resending to broonie@kernel.org; other email address got message too big for mailbox]
On 2/17/20 11:04 PM, Randy Dunlap wrote:
> On 2/17/20 8:28 PM, Stephen Rothwell wrote:
>> Hi all,
>>
>> Changes since 20200217:
>>
>
> on x86_64:
>
> WARNING: unmet direct dependencies detected for SND_SOC_WM5110
> Depends on [n]: SOUND [=y] && !UML && SND [=y] && SND_SOC [=y] && MFD_WM5110 [=n]
> Selected by [y]:
> - SND_SOC_BELLS [=y] && SOUND [=y] && !UML && SND [=y] && SND_SOC [=y] && SND_SOC_SAMSUNG [=y] && MFD_ARIZONA [=y] && I2C [=y] && SPI_MASTER [=y] && (MACH_WLF_CRAGG_6410 || COMPILE_TEST [=y])
> - SND_SOC_SAMSUNG_TM2_WM5110 [=y] && SOUND [=y] && !UML && SND [=y] && SND_SOC [=y] && SND_SOC_SAMSUNG [=y] && MFD_ARIZONA [=y] && I2C [=y] && SPI_MASTER [=y] && (GPIOLIB [=y] || COMPILE_TEST [=y])
>
>
> Full randconfig file is attached.
>
--
~Randy
Reported-by: Randy Dunlap <rdunlap@infradead.org>
next prev parent reply other threads:[~2020-02-18 7:06 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-18 4:28 linux-next: Tree for Feb 18 Stephen Rothwell
2020-02-18 6:31 ` linux-next: Tree for Feb 18 (drivers/staging/media/rkisp1/) Randy Dunlap
2020-02-18 12:49 ` Helen Koike
2020-02-18 7:04 ` linux-next: Tree for Feb 18 (sound/soc/codecs/wm5110.c) Randy Dunlap
2020-02-18 7:05 ` Randy Dunlap [this message]
2020-02-18 10:09 ` Charles Keepax
2020-02-18 11:31 ` Mark Brown
2020-02-18 13:09 ` Charles Keepax
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=c2273472-18af-e206-c942-fd460e0d192c@infradead.org \
--to=rdunlap@infradead.org \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=patches@opensource.cirrus.com \
--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;
as well as URLs for NNTP newsgroup(s).