From: Mark Brown <broonie@kernel.org>
To: Pierre-Louis Bossart <pierre-louis.bossart@linux.intel.com>
Cc: linux-s390 <linux-s390@vger.kernel.org>,
ALSA Development Mailing List <alsa-devel@alsa-project.org>,
Linux-sh list <linux-sh@vger.kernel.org>,
Randy Dunlap <rdunlap@infradead.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Geert Uytterhoeven <geert@linux-m68k.org>,
linuxppc-dev <linuxppc-dev@lists.ozlabs.org>
Subject: Re: Build regressions/improvements in v4.20-rc1 (sound/pci/hda/patch_ca0132.c)
Date: Tue, 6 Nov 2018 15:46:59 +0000 [thread overview]
Message-ID: <20181106154659.GA31950@sirena.org.uk> (raw)
In-Reply-To: <eccd20fa-5be3-957d-7905-9cc4021ba94e@linux.intel.com>
[-- Attachment #1.1: Type: text/plain, Size: 744 bytes --]
On Tue, Nov 06, 2018 at 08:56:39AM -0600, Pierre-Louis Bossart wrote:
> > However, looking at what else can enable SND_HDA, I think it should be
> > select SND_SOC_HDAC_HDA if SND_PCI || ARCH_TEGRA
> This codec can only be used by the Skylake driver (and the upcoming SOF
> one). For Tegra this module will never be used unless they follow the same
> path of enabling ASoC to deal with the HDaudio codecs instead of the legacy.
> Likewise HDAC_HDMI will only work on Intel platforms for now.
_ALL_CODECS is a build coverage option, not a useful configuration
option. We should be building things in as many different
configurations as possible so that it's easier for people to get build
coverage when making subsystem wide changes.
[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
[-- Attachment #2: Type: text/plain, Size: 0 bytes --]
next prev parent reply other threads:[~2018-11-06 15:46 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20181105220559.27458-1-geert@linux-m68k.org>
2018-11-05 22:12 ` Build regressions/improvements in v4.20-rc1 Geert Uytterhoeven
2018-11-06 1:04 ` Build regressions/improvements in v4.20-rc1 (sound/pci/hda/patch_ca0132.c) Randy Dunlap
2018-11-06 8:01 ` Geert Uytterhoeven
2018-11-06 14:56 ` [alsa-devel] " Pierre-Louis Bossart
2018-11-06 15:25 ` Geert Uytterhoeven
2018-11-06 15:46 ` Mark Brown [this message]
2018-11-06 16:18 ` Takashi Iwai
2018-11-07 8:44 ` Geert Uytterhoeven
2018-11-07 9:41 ` Takashi Iwai
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=20181106154659.GA31950@sirena.org.uk \
--to=broonie@kernel.org \
--cc=alsa-devel@alsa-project.org \
--cc=geert@linux-m68k.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-s390@vger.kernel.org \
--cc=linux-sh@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=pierre-louis.bossart@linux.intel.com \
--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