From: Randy Dunlap <rdunlap@infradead.org>
To: broonie@kernel.org, Linux Next Mailing List <linux-next@vger.kernel.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
alsa-devel@alsa-project.org, Mark Brown <broonie@kernel.org>,
Liam Girdwood <lgirdwood@gmail.com>,
Pierre-Louis Bossart <pierre-louis.bossart@linux.intel.com>,
Ajit Kumar Pandey <AjitKumar.Pandey@amd.com>
Subject: Re: linux-next: Tree for Dec 13 (SND_AMD_ACP_CONFIG)
Date: Mon, 13 Dec 2021 22:20:46 -0800 [thread overview]
Message-ID: <8ff9d4b2-1905-2efa-cb86-e8f6cef06ef2@infradead.org> (raw)
In-Reply-To: <20211214030215.3181149-1-broonie@kernel.org>
[-- Attachment #1: Type: text/plain, Size: 667 bytes --]
On 12/13/21 19:02, broonie@kernel.org wrote:
> Hi all,
>
> Non-merge commits (relative to Linus' tree): 5960
> 6555 files changed, 277265 insertions(+), 120864 deletions(-)
>
> ----------------------------------------------------------------------------
>
on i386 or x86_64:
when # CONFIG_ACPI is not set,
so SND_SOC_ACPI is not set:
WARNING: unmet direct dependencies detected for SND_AMD_ACP_CONFIG
Depends on [n]: SOUND [=y] && !UML && SND [=y] && SND_SOC [=y] && SND_SOC_ACPI [=n]
Selected by [y]:
- SND_SOC_AMD_ACP_COMMON [=y] && SOUND [=y] && !UML && SND [=y] && SND_SOC [=y] && X86 [=y] && PCI [=y]
Full randconfig file is attached
--
~Randy
[-- Attachment #2: config-r1848.gz --]
[-- Type: application/gzip, Size: 30820 bytes --]
next prev parent reply other threads:[~2021-12-14 6:20 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-14 3:02 linux-next: Tree for Dec 13 broonie
2021-12-14 6:20 ` Randy Dunlap [this message]
2021-12-14 13:51 ` linux-next: Tree for Dec 13 (SND_AMD_ACP_CONFIG) Pierre-Louis Bossart
2021-12-14 16:26 ` Randy Dunlap
2021-12-14 17:21 ` Daniel Baluta
2021-12-14 17:25 ` Pierre-Louis Bossart
2021-12-14 17:40 ` Daniel Baluta
2021-12-14 11:44 ` linux-next: Tree for Dec 13 Andy Shevchenko
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=8ff9d4b2-1905-2efa-cb86-e8f6cef06ef2@infradead.org \
--to=rdunlap@infradead.org \
--cc=AjitKumar.Pandey@amd.com \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@kernel.org \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=pierre-louis.bossart@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).