From: Randy Dunlap <rdunlap@infradead.org>
To: Stephen Rothwell <sfr@canb.auug.org.au>,
Linux Next Mailing List <linux-next@vger.kernel.org>,
Hui Wang <hui.wang@canonical.com>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Keyon Jie <yang.jie@linux.intel.com>,
sound-open-firmware@alsa-project.org,
Pierre-Louis Bossart <pierre-louis.bossart@linux.intel.com>,
Liam Girdwood <lgirdwood@gmail.com>,
Ranjani Sridharan <ranjani.sridharan@linux.intel.com>,
Kai Vehmanen <kai.vehmanen@linux.intel.com>,
Daniel Baluta <daniel.baluta@nxp.com>,
Mark Brown <broonie@kernel.org>
Subject: Re: linux-next: Tree for Dec 3 (sound/soc/sof/intel/hda-codec.c)
Date: Fri, 3 Dec 2021 16:34:56 -0800 [thread overview]
Message-ID: <66206234-d0b9-da64-c75d-4ea73dda5ff9@infradead.org> (raw)
In-Reply-To: <20211203194709.3bcfb3a7@canb.auug.org.au>
[-- Attachment #1: Type: text/plain, Size: 687 bytes --]
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.
--
~Randy
[-- Attachment #2: config-r1651.gz --]
[-- Type: application/gzip, Size: 46130 bytes --]
next prev parent reply other threads:[~2021-12-04 0:35 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 ` Randy Dunlap [this message]
2021-12-04 0:45 ` [Sound-open-firmware] linux-next: Tree for Dec 3 (sound/soc/sof/intel/hda-codec.c) 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=66206234-d0b9-da64-c75d-4ea73dda5ff9@infradead.org \
--to=rdunlap@infradead.org \
--cc=broonie@kernel.org \
--cc=daniel.baluta@nxp.com \
--cc=hui.wang@canonical.com \
--cc=kai.vehmanen@linux.intel.com \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=pierre-louis.bossart@linux.intel.com \
--cc=ranjani.sridharan@linux.intel.com \
--cc=sfr@canb.auug.org.au \
--cc=sound-open-firmware@alsa-project.org \
--cc=yang.jie@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
all inboxes | Powered by JetHome®