From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Mark Brown <broonie@kernel.org>, Liam Girdwood <lgirdwood@gmail.com>
Cc: Linux Next Mailing List <linux-next@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: linux-next: build failure after merge of the sound-asoc-fixes tree
Date: Wed, 13 Nov 2019 08:10:35 +1100 [thread overview]
Message-ID: <20191113081035.7e7f9bc2@canb.auug.org.au> (raw)
[-- Attachment #1: Type: text/plain, Size: 956 bytes --]
Hi all,
After merging the sound-asoc-fixes tree, today's linux-next build
(x86_64 allmodconfig) failed like this:
sound/soc/sof/sof-pci-dev.c:116:15: error: 'snd_soc_acpi_intel_cfl_machines' undeclared here (not in a function); did you mean 'snd_soc_acpi_intel_cnl_machines'?
116 | .machines = snd_soc_acpi_intel_cfl_machines,
| ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
| snd_soc_acpi_intel_cnl_machines
sound/soc/sof/sof-pci-dev.c:136:15: error: 'snd_soc_acpi_intel_cml_machines' undeclared here (not in a function); did you mean 'snd_soc_acpi_intel_cnl_machines'?
136 | .machines = snd_soc_acpi_intel_cml_machines,
| ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
| snd_soc_acpi_intel_cnl_machines
Caused by commit
1d3e9077307f ("ASoC: SOF: Intel: Fix CFL and CML FW nocodec binary names.")
I have reverted that commit for today.
--
Cheers,
Stephen Rothwell
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next reply other threads:[~2019-11-12 21:10 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-12 21:10 Stephen Rothwell [this message]
2019-11-14 22:34 ` linux-next: build failure after merge of the sound-asoc-fixes tree Stephen Rothwell
2019-11-18 15:58 ` Mark Brown
2019-11-18 16:47 ` Pierre-Louis Bossart
2019-11-18 19:14 ` Mark Brown
2019-11-19 3:15 ` Stephen Rothwell
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=20191113081035.7e7f9bc2@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=broonie@kernel.org \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.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).