From: patchwork-bot+bluetooth@kernel.org
To: Bastien Nocera <hadess@hadess.net>
Cc: linux-bluetooth@vger.kernel.org, arun@accosted.net
Subject: Re: [PATCH BlueZ] transport: Fix build with VCP support disabled
Date: Wed, 17 Sep 2025 13:30:07 +0000 [thread overview]
Message-ID: <175811580798.1623615.10398322340567444179.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20250916230017.2216629-1-hadess@hadess.net>
Hello:
This patch was applied to bluetooth/bluez.git (master)
by Luiz Augusto von Dentz <luiz.von.dentz@intel.com>:
On Wed, 17 Sep 2025 01:00:14 +0200 you wrote:
> $ $ ./bootstrap-configure --enable-a2dp --enable-avrcp --enable-experimental --enable-asha --disable-vcp && make
> [...]
> /usr/bin/ld: profiles/audio/bluetoothd-transport.o: in function `transport_bap_set_volume':
> profiles/audio/transport.c:2275:(.text.transport_bap_set_volume+0x11): undefined reference to `bt_audio_vcp_set_volume'
> /usr/bin/ld: profiles/audio/bluetoothd-transport.o: in function `transport_bap_get_volume':
> profiles/audio/transport.c:2266:(.text.transport_bap_get_volume+0x9): undefined reference to `bt_audio_vcp_get_volume'
>
> [...]
Here is the summary with links:
- [BlueZ] transport: Fix build with VCP support disabled
https://git.kernel.org/pub/scm/bluetooth/bluez.git/?id=c6dcf6b71450
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2025-09-17 13:30 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-16 23:00 [PATCH BlueZ] transport: Fix build with VCP support disabled Bastien Nocera
2025-09-17 0:29 ` [BlueZ] " bluez.test.bot
2025-09-17 13:30 ` patchwork-bot+bluetooth [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=175811580798.1623615.10398322340567444179.git-patchwork-notify@kernel.org \
--to=patchwork-bot+bluetooth@kernel.org \
--cc=arun@accosted.net \
--cc=hadess@hadess.net \
--cc=linux-bluetooth@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