From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Scott Bruce <smbruce@gmail.com>
Cc: stable@vger.kernel.org
Subject: Re: WIP 5.15.5-rc1 build failure in sound/soc/sof/intel/hda-dai.c
Date: Wed, 24 Nov 2021 19:19:04 +0100 [thread overview]
Message-ID: <YZ6CGCn0cZ6Rr8gp@kroah.com> (raw)
In-Reply-To: <CAPOoXdHhLdkP9KE4_9pPzUTdpFbN15wQp9SshJfvz1SxZWsRbA@mail.gmail.com>
On Wed, Nov 24, 2021 at 08:57:39AM -0800, Scott Bruce wrote:
> It looks like the current work in progress branch for 5.15.5-rc1
> picked up fe1bda72c1e8 "ASoC: SOF: Intel: hda-dai: fix potential
> locking issue" without also picking 868ddfcef31f "ALSA: hda:
> hdac_ext_stream: fix potential locking issues" from master. This
> causes builds to fail on x86_64 using clang:
>
> ...
> CC [M] drivers/misc/eeprom/at25.o
> CC [M] drivers/block/pktcdvd.o
> LTO [M] sound/soc/codecs/snd-soc-max98088.lto.o
> sound/soc/sof/intel/hda-dai.c:111:4: error: implicit declaration of
> function 'snd_hdac_ext_stream_decouple_locked'
> [-Werror,-Wimplicit-function-declaration]
> snd_hdac_ext_stream_decouple_locked(bus, res, true);
> ^
> sound/soc/sof/intel/hda-dai.c:111:4: note: did you mean
> 'snd_hdac_ext_stream_decouple'?
> ./include/sound/hdaudio_ext.h:91:6: note:
> 'snd_hdac_ext_stream_decouple' declared here
> void snd_hdac_ext_stream_decouple(struct hdac_bus *bus,
> ^
> 1 error generated.
> make[4]: *** [scripts/Makefile.build:277: sound/soc/sof/intel/hda-dai.o] Error 1
> make[3]: *** [scripts/Makefile.build:540: sound/soc/sof/intel] Error 2
> make[2]: *** [scripts/Makefile.build:540: sound/soc/sof] Error 2
> make[2]: *** Waiting for unfinished jobs....
> AR drivers/misc/cb710/built-in.a
> CC [M] drivers/misc/cb710/core.o
> CC [M] net/netfilter/xt_nfacct.o
> ...
>
> After cherry-picking the second commit (868ddfcef31f) builds complete normally.
Now added, thanks.
> In case it's relevant there's a third commit in this same series
> that's also not included: 1465d06a6d85, "ALSA: hda: hdac_stream: fix
> potential locking issue in snd_hdac_stream_assign()".
I've queued that up now as well, thanks!
greg k-h
prev parent reply other threads:[~2021-11-24 18:19 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-24 16:57 WIP 5.15.5-rc1 build failure in sound/soc/sof/intel/hda-dai.c Scott Bruce
2021-11-24 18:19 ` Greg Kroah-Hartman [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=YZ6CGCn0cZ6Rr8gp@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=smbruce@gmail.com \
--cc=stable@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