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>
Cc: ALSA Development Mailing List <alsa-devel@alsa-project•org>,
Mark Brown <broonie@kernel•org>,
Linux Kernel Mailing List <linux-kernel@vger•kernel.org>
Subject: Re: linux-next: Tree for Jul 15 (sof-client-ipc-flood-test.c)
Date: Mon, 18 Jul 2022 11:28:44 -0500 [thread overview]
Message-ID: <eacfa436-fb01-9f0f-8bc0-6d857653bed8@linux.intel.com> (raw)
In-Reply-To: <d9e2d97c-12a5-5846-a9dc-4c7c0c10988e@infradead.org>
On 7/15/22 17:49, Randy Dunlap wrote:
>
>
> On 7/15/22 05:52, Stephen Rothwell wrote:
>> Hi all,
>>
>> Changes since 20220714:
>>
>
> on x86_64:
>
> ld: vmlinux.o: in function `sof_ipc_flood_probe':
> sof-client-ipc-flood-test.c:(.text+0xb961d4): undefined reference to `sof_client_get_debugfs_root'
> ld: vmlinux.o: in function `sof_ipc_flood_dfs_open':
> sof-client-ipc-flood-test.c:(.text+0xb963ed): undefined reference to `sof_client_get_fw_state'
> ld: vmlinux.o: in function `sof_ipc_flood_dfs_write':
> sof-client-ipc-flood-test.c:(.text+0xb9689a): undefined reference to `sof_client_ipc_tx_message'
>
>
> Full randconfig file is attached.
Thanks Randy, I reproduced the issue, it was also reported by the Intel
bot. I added all the configs here:
https://github.com/thesofproject/linux/issues/3768
The issue is that the sof-client helpers are compiled with the same
setting as the SOF core, but the clients can be compiled as built-in,
that cannot possibly work.
It's peak vacation season so it'll take a couple of weeks to be
fixed/reviewed, but we'll fix this.
-Pierre
prev parent reply other threads:[~2022-07-18 16:29 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-15 12:52 linux-next: Tree for Jul 15 Stephen Rothwell
2022-07-15 22:39 ` linux-next: Tree for Jul 15 (nfsd) Randy Dunlap
2022-07-15 22:49 ` linux-next: Tree for Jul 15 (sof-client-ipc-flood-test.c) Randy Dunlap
2022-07-18 16:28 ` 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=eacfa436-fb01-9f0f-8bc0-6d857653bed8@linux.intel.com \
--to=pierre-louis.bossart@linux$(echo .)intel.com \
--cc=alsa-devel@alsa-project$(echo .)org \
--cc=broonie@kernel$(echo .)org \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=rdunlap@infradead$(echo .)org \
--cc=sfr@canb$(echo .)auug.org.au \
/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