From: Mark Brown <broonie@kernel.org>
To: Pierre-Louis Bossart <pierre-louis.bossart@linux.intel.com>
Cc: "Cezary Rojewski" <cezary.rojewski@intel.com>,
"kernel test robot" <lkp@intel.com>,
alsa-devel@alsa-project.org,
"Liam Girdwood" <lgirdwood@gmail.com>,
"Takashi Iwai" <tiwai@suse.com>,
"Amadeusz Sławiński" <amadeuszx.slawinski@linux.intel.com>
Subject: Re: [PATCH] ASoC: Intel: avs: Depend on CONFIG_ACPI
Date: Tue, 26 Apr 2022 18:08:35 +0100 [thread overview]
Message-ID: <YmgnE/HKNmI+agNs@sirena.org.uk> (raw)
In-Reply-To: <eab567f0-73a4-bf23-76bf-8d576fa942f0@linux.intel.com>
[-- Attachment #1: Type: text/plain, Size: 569 bytes --]
On Tue, Apr 26, 2022 at 08:33:57AM -0500, Pierre-Louis Bossart wrote:
> On 4/26/22 06:54, Amadeusz Sławiński wrote:
> > - depends on (X86 && ACPI) || COMPILE_TEST
> > - depends on PCI
> > + depends on X86 || COMPILE_TEST
> > + depends on PCI && ACPI
> > depends on COMMON_CLK
> > select SND_SOC_ACPI
> select SND_SOC_ACPI if ACPI should work, that's what we do for SOF.
That also looks sensible - it's probably good if both users do the same
thing here so can someone send a patch for that please? Sorry for not
noticing that earlier Amadeusz.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2022-04-26 17:10 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-26 11:54 [PATCH] ASoC: Intel: avs: Depend on CONFIG_ACPI Amadeusz Sławiński
2022-04-26 13:33 ` Pierre-Louis Bossart
2022-04-26 17:08 ` Mark Brown [this message]
2022-04-26 18:07 ` Cezary Rojewski
2022-04-26 18:25 ` Mark Brown
2022-04-26 18:26 ` Pierre-Louis Bossart
2022-04-26 18:38 ` Mark Brown
2022-04-26 18:42 ` Pierre-Louis Bossart
2022-04-26 19:07 ` Amadeusz Sławiński
2022-04-26 19:16 ` Pierre-Louis Bossart
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=YmgnE/HKNmI+agNs@sirena.org.uk \
--to=broonie@kernel.org \
--cc=alsa-devel@alsa-project.org \
--cc=amadeuszx.slawinski@linux.intel.com \
--cc=cezary.rojewski@intel.com \
--cc=lgirdwood@gmail.com \
--cc=lkp@intel.com \
--cc=pierre-louis.bossart@linux.intel.com \
--cc=tiwai@suse.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.