From: Pierre-Louis Bossart <pierre-louis.bossart@linux.intel.com>
To: Mark Brown <broonie@kernel.org>,
Cezary Rojewski <cezary.rojewski@intel.com>
Cc: alsa-devel@alsa-project.org, "kernel test robot" <lkp@intel.com>,
"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 13:26:08 -0500 [thread overview]
Message-ID: <ba9e90de-94ad-d6c9-b6df-1fe6f802e9d6@linux.intel.com> (raw)
In-Reply-To: <Ymg5CAbwf/UxUOff@sirena.org.uk>
On 4/26/22 13:25, Mark Brown wrote:
> On Tue, Apr 26, 2022 at 08:07:22PM +0200, Cezary Rojewski wrote:
>
>> Would you like the change proposed by Pierre to be part of this patch or a
>> separate one?
>
> Either is fine.
>
>> Also, I assume the above code does not change, just:
>> s/select SND_SOC_ACPI/select SND_SOC_ACPI if ACPI/
>
>> is applied on top of what's already in the patch. Is my deduction correct?
>
> AIUI the current patch and associated hard dependency on ACPI could be
> dropped but I've not checked or thought too deeply about it
my suggestion was the following:
depends on PCI
depends on COMMON_CLK
select SND_SOC_ACPI if ACPI
next prev parent reply other threads:[~2022-04-26 18:27 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
2022-04-26 18:07 ` Cezary Rojewski
2022-04-26 18:25 ` Mark Brown
2022-04-26 18:26 ` Pierre-Louis Bossart [this message]
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=ba9e90de-94ad-d6c9-b6df-1fe6f802e9d6@linux.intel.com \
--to=pierre-louis.bossart@linux.intel.com \
--cc=alsa-devel@alsa-project.org \
--cc=amadeuszx.slawinski@linux.intel.com \
--cc=broonie@kernel.org \
--cc=cezary.rojewski@intel.com \
--cc=lgirdwood@gmail.com \
--cc=lkp@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.