From: Oder Chiou <oder_chiou@realtek.com>
To: Mark Brown <broonie@kernel.org>
Cc: "lgirdwood@gmail.com" <lgirdwood@gmail.com>,
"linux-sound@vger.kernel.org" <linux-sound@vger.kernel.org>,
"Flove(HsinFu)" <flove@realtek.com>,
"Shuming [范書銘]" <shumingf@realtek.com>,
"Jack Yu" <jack.yu@realtek.com>,
"Derek [方德義]" <derek.fang@realtek.com>
Subject: RE: [PATCH] ASoC: rt5575: Fix undefined references to SPI functions
Date: Wed, 28 Jan 2026 05:02:56 +0000 [thread overview]
Message-ID: <5c56f5d1cfc04d2cb9cb897fb3aecabe@realtek.com> (raw)
In-Reply-To: <e259f5f3-072f-4b2d-9191-9a0717212beb@sirena.org.uk>
> -----Original Message-----
> From: Mark Brown <broonie@kernel.org>
> Sent: Tuesday, January 27, 2026 5:22 AM
> To: Oder Chiou <oder_chiou@realtek.com>
> Cc: lgirdwood@gmail.com; linux-sound@vger.kernel.org;
> alsa-devel@alsa-project.org; Flove(HsinFu) <flove@realtek.com>; Shuming [范
> 書銘] <shumingf@realtek.com>; Jack Yu <jack.yu@realtek.com>; Derek [方德
> 義] <derek.fang@realtek.com>; kernel test robot <lkp@intel.com>
> Subject: Re: [PATCH] ASoC: rt5575: Fix undefined references to SPI functions
>
> On Mon, Jan 26, 2026 at 01:17:58PM +0800, Oder Chiou wrote:
> > The kernel test robot reported the following build errors:
>
> This breaks an x86 allmodconfig build:
>
> ERROR: modpost: "rt5575_spi_fw_load" [sound/soc/codecs/snd-soc-rt5575.ko]
> undefi
> ned!
> ERROR: modpost: "rt5575_spi_get_device"
> [sound/soc/codecs/snd-soc-rt5575.ko] und
> efined!
I tried to reproduce the reported modpost error with make allmodconfig
on my local machine, but the build passed successfully.
In my generated .config from allmodconfig, I have:
CONFIG_SND_SOC_RT5575=m
CONFIG_SND_SOC_RT5575_SPI=y
I also attempted to manually force CONFIG_SND_SOC_RT5575_SPI=m to see if
that triggered the issue. However, Kbuild produced the following warning
and automatically reverted it to 'y' (since it is a boolean in Kconfig):
.config:11393:warning: symbol value 'm' invalid for SND_SOC_RT5575_SPI
Could you please check if there might be a mismatch in the applied
patches or a specific .config state I should be aware of? I want to make
sure I am testing under the same conditions.
Thanks
prev parent reply other threads:[~2026-01-28 5:03 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-26 5:17 [PATCH] ASoC: rt5575: Fix undefined references to SPI functions Oder Chiou
2026-01-26 21:22 ` Mark Brown
2026-01-28 5:02 ` Oder Chiou [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=5c56f5d1cfc04d2cb9cb897fb3aecabe@realtek.com \
--to=oder_chiou@realtek.com \
--cc=broonie@kernel.org \
--cc=derek.fang@realtek.com \
--cc=flove@realtek.com \
--cc=jack.yu@realtek.com \
--cc=lgirdwood@gmail.com \
--cc=linux-sound@vger.kernel.org \
--cc=shumingf@realtek.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