From: Pierre-Louis Bossart <pierre-louis.bossart@linux•intel.com>
To: Randy Dunlap <rdunlap@infradead•org>,
Stephen Rothwell <sfr@canb•auug.org.au>,
Linux Next Mailing List <linux-next@vger•kernel.org>,
Hui Wang <hui.wang@canonical•com>
Cc: Kai Vehmanen <kai.vehmanen@linux•intel.com>,
Liam Girdwood <lgirdwood@gmail•com>,
Linux Kernel Mailing List <linux-kernel@vger•kernel.org>,
Keyon Jie <yang.jie@linux•intel.com>,
Ranjani Sridharan <ranjani.sridharan@linux•intel.com>,
Mark Brown <broonie@kernel•org>,
Daniel Baluta <daniel.baluta@nxp•com>,
sound-open-firmware@alsa-project•org
Subject: Re: [Sound-open-firmware] linux-next: Tree for Dec 3 (sound/soc/sof/intel/hda-codec.c)
Date: Fri, 3 Dec 2021 18:45:36 -0600 [thread overview]
Message-ID: <e2fb7287-cb60-319c-33b2-8c49b755107c@linux.intel.com> (raw)
In-Reply-To: <66206234-d0b9-da64-c75d-4ea73dda5ff9@infradead.org>
On 12/3/21 6:34 PM, Randy Dunlap wrote:
>
>
> On 12/3/21 00:47, Stephen Rothwell wrote:
>> Hi all,
>>
>> News: I will (probably) do no linux-next releases between Dec 9 and Dec
>> 19, inclusive (i.e. that means 3 releases next week and none the week
>> after).
>>
>> Changes since 20211202:
>>
>
> on i386:
> # CONFIG_SND_SOC_SOF_HDA_AUDIO_CODEC is not set
>
> ../sound/soc/sof/intel/hda-codec.c: In function ‘hda_codec_probe’:
> ../sound/soc/sof/intel/hda-codec.c:132:35: error: ‘CODEC_PROBE_RETRIES’ undeclared (first use in this function); did you mean ‘DEV_PROP_STRING’?
> } while (resp == -1 && retry++ < CODEC_PROBE_RETRIES);
> ^~~~~~~~~~~~~~~~~~~
>
>
> Full randconfig file is attached.
Thanks Randy, Kai provided a fix already, see "ASoC: SOF: Intel: fix
build issue related to CODEC_PROBE_ENTRIES" on alsa-devel.
prev parent reply other threads:[~2021-12-04 0:45 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-03 8:47 linux-next: Tree for Dec 3 Stephen Rothwell
2021-12-04 0:34 ` linux-next: Tree for Dec 3 (sound/soc/sof/intel/hda-codec.c) Randy Dunlap
2021-12-04 0:45 ` Pierre-Louis Bossart [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=e2fb7287-cb60-319c-33b2-8c49b755107c@linux.intel.com \
--to=pierre-louis.bossart@linux$(echo .)intel.com \
--cc=broonie@kernel$(echo .)org \
--cc=daniel.baluta@nxp$(echo .)com \
--cc=hui.wang@canonical$(echo .)com \
--cc=kai.vehmanen@linux$(echo .)intel.com \
--cc=lgirdwood@gmail$(echo .)com \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=ranjani.sridharan@linux$(echo .)intel.com \
--cc=rdunlap@infradead$(echo .)org \
--cc=sfr@canb$(echo .)auug.org.au \
--cc=sound-open-firmware@alsa-project$(echo .)org \
--cc=yang.jie@linux$(echo .)intel.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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