linux-next.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Pierre-Louis Bossart <pierre-louis.bossart@linux.intel.com>
To: Daniel Baluta <daniel.baluta@gmail.com>,
	Randy Dunlap <rdunlap@infradead.org>
Cc: Linux-ALSA <alsa-devel@alsa-project.org>,
	Ajit Kumar Pandey <AjitKumar.Pandey@amd.com>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Liam Girdwood <lgirdwood@gmail.com>,
	Mark Brown <broonie@kernel.org>,
	Linux Next Mailing List <linux-next@vger.kernel.org>
Subject: Re: linux-next: Tree for Dec 13 (SND_AMD_ACP_CONFIG)
Date: Tue, 14 Dec 2021 11:25:57 -0600	[thread overview]
Message-ID: <11ed7f0f-ad5a-cae1-035c-23e5d3736818@linux.intel.com> (raw)
In-Reply-To: <CAEnQRZB9E4uBDuUidiJ+QJnQhGZp43jig4q93Pkw3pSr=K48YQ@mail.gmail.com>



On 12/14/21 11:21 AM, Daniel Baluta wrote:
> Hi Randy,
> 
> This should be fixed by https://github.com/thesofproject/linux/pull/3284

no, this was precisely the change that exposed a new problem.

https://github.com/thesofproject/linux/pull/3335 contains the suggested
fix posted earlier. We should know tomorrow if the 0day bot finds any
other issues.

> 
> Let me quickly send this to alsa-devel.
> 
> 
> On Tue, Dec 14, 2021 at 12:08 PM Randy Dunlap <rdunlap@infradead.org> wrote:
>>
>>
>>
>> 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

  reply	other threads:[~2021-12-14 17:26 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 ` linux-next: Tree for Dec 13 (SND_AMD_ACP_CONFIG) Randy Dunlap
2021-12-14 13:51   ` 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 [this message]
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=11ed7f0f-ad5a-cae1-035c-23e5d3736818@linux.intel.com \
    --to=pierre-louis.bossart@linux.intel.com \
    --cc=AjitKumar.Pandey@amd.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=broonie@kernel.org \
    --cc=daniel.baluta@gmail.com \
    --cc=lgirdwood@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=rdunlap@infradead.org \
    /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).