From: Mark Brown <broonie@kernel.org>
To: Pierre-Louis Bossart <pierre-louis.bossart@linux.intel.com>
Cc: Liam Girdwood <liam.r.girdwood@linux.intel.com>,
alsa-devel@alsa-project.org, kbuild-all@lists.01.org,
kbuild test robot <lkp@intel.com>
Subject: Re: [alsa-devel] [asoc:for-5.4 438/441] 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'?
Date: Mon, 18 Nov 2019 15:55:04 +0000 [thread overview]
Message-ID: <20191118155504.GF9761@sirena.org.uk> (raw)
In-Reply-To: <0d89e1df-81e7-ce5f-0709-add84ecf6295@linux.intel.com>
[-- Attachment #1.1: Type: text/plain, Size: 494 bytes --]
On Mon, Nov 18, 2019 at 09:31:12AM -0600, Pierre-Louis Bossart wrote:
> Looks like the for-5.4 branch did not pick up all the patches from the
> series [PATCH 0/3] ASoC: Intel/SOF: split CFL, CNL, CML firmware names
>
> it's missing:
> [PATCH 1/3] ASoC: Intel: acpi-match: split CNL tables in three
> [PATCH 3/3] ASoC: SOF: Intel: hda: use fallback for firmware name
Only one of those looks like a fix... I've reverted the commit from
5.4. Stephen reported this last week...
[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
[-- Attachment #2: Type: text/plain, Size: 161 bytes --]
_______________________________________________
Alsa-devel mailing list
Alsa-devel@alsa-project.org
https://mailman.alsa-project.org/mailman/listinfo/alsa-devel
prev parent reply other threads:[~2019-11-18 15:56 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-17 2:02 [alsa-devel] [asoc:for-5.4 438/441] 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'? kbuild test robot
2019-11-18 15:31 ` Pierre-Louis Bossart
2019-11-18 15:55 ` Mark Brown [this message]
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=20191118155504.GF9761@sirena.org.uk \
--to=broonie@kernel.org \
--cc=alsa-devel@alsa-project.org \
--cc=kbuild-all@lists.01.org \
--cc=liam.r.girdwood@linux.intel.com \
--cc=lkp@intel.com \
--cc=pierre-louis.bossart@linux.intel.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 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).