public inbox for linux-bluetooth@vger.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+bluetooth@kernel.org
To: =?utf-8?b?RnLDqWTDqXJpYyBEYW5pcyA8ZnJlZGVyaWMuZGFuaXNAY29sbGFib3JhLmNvbT4=?=@aws-us-west-2-korg-oddjob-rhel9-1.codeaurora.org
Cc: linux-bluetooth@vger.kernel.org
Subject: Re: [PATCH BlueZ] client/btpclient: Add BTP_OP_BAP_DISCOVER support
Date: Mon, 20 Apr 2026 22:00:01 +0000	[thread overview]
Message-ID: <177672240132.1802062.9137474047862464607.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260416184914.145135-1-frederic.danis@collabora.com>

Hello:

This patch was applied to bluetooth/bluez.git (master)
by Luiz Augusto von Dentz <luiz.von.dentz@intel.com>:

On Thu, 16 Apr 2026 20:49:14 +0200 you wrote:
> BAP/CL/CGGIT/SER/BV-01-C expects IUT to discover the services before
> continuation.
> 
> This reduces connection time for the BAP tests.
> ---
>  Makefile.tools          |   1 +
>  client/btpclient/bap.c  | 109 ++++++++++++++++++++++++++++++++++++++++
>  client/btpclient/bap.h  |  13 +++++
>  client/btpclient/core.c |  15 ++++++
>  src/shared/btp.h        |  16 ++++++
>  5 files changed, 154 insertions(+)
>  create mode 100644 client/btpclient/bap.c
>  create mode 100644 client/btpclient/bap.h

Here is the summary with links:
  - [BlueZ] client/btpclient: Add BTP_OP_BAP_DISCOVER support
    https://git.kernel.org/pub/scm/bluetooth/bluez.git/?id=b57658668c7c

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



      parent reply	other threads:[~2026-04-20 22:00 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-04-16 18:49 [PATCH BlueZ] client/btpclient: Add BTP_OP_BAP_DISCOVER support Frédéric Danis
2026-04-16 20:29 ` [BlueZ] " bluez.test.bot
2026-04-20 22:00 ` 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=177672240132.1802062.9137474047862464607.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+bluetooth@kernel.org \
    --cc==?utf-8?b?RnLDqWTDqXJpYyBEYW5pcyA8ZnJlZGVyaWMuZGFuaXNAY29sbGFib3JhLmNvbT4=?=@aws-us-west-2-korg-oddjob-rhel9-1.codeaurora.org \
    --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