public inbox for linux-bluetooth@vger.kernel.org
 help / color / mirror / Atom feed
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 A2DP support disabled
Date: Thu, 18 Sep 2025 13:30:06 +0000	[thread overview]
Message-ID: <175820220698.2414053.11560029662948810614.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20250912003233.931520-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 Fri, 12 Sep 2025 02:32:19 +0200 you wrote:
> $ ./bootstrap-configure --disable-a2dp && make
> [...]
> profiles/audio/transport.c: In function ‘media_transport_update_delay’:
> profiles/audio/transport.c:2653:33: error: implicit declaration of function ‘a2dp_avdtp_get’ [-Wimplicit-function-declaration]
>  2653 |                 a2dp->session = a2dp_avdtp_get(transport->device);
>       |                                 ^~~~~~~~~~~~~~
> profiles/audio/transport.c:2653:31: error: assignment to ‘struct avdtp *’ from ‘int’ makes pointer from integer without a cast [-Wint-conversion]
>  2653 |                 a2dp->session = a2dp_avdtp_get(transport->device);
>       |                               ^
> 
> [...]

Here is the summary with links:
  - [BlueZ] transport: Fix build with A2DP support disabled
    https://git.kernel.org/pub/scm/bluetooth/bluez.git/?id=61d3e447f9d4

You are awesome, thank you!
-- 
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html



      parent reply	other threads:[~2025-09-18 13:30 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-09-12  0:32 [PATCH BlueZ] transport: Fix build with A2DP support disabled Bastien Nocera
2025-09-12  2:19 ` [BlueZ] " bluez.test.bot
2025-09-18 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=175820220698.2414053.11560029662948810614.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