From: patchwork-bot+bluetooth@kernel.org
To: Luiz Augusto von Dentz <luiz.dentz@gmail.com>
Cc: linux-bluetooth@vger.kernel.org
Subject: Re: [PATCH BlueZ 1/2] bthost: Add destroy callback to bthost_add_iso_hook
Date: Mon, 22 Aug 2022 22:40:15 +0000 [thread overview]
Message-ID: <166120801512.10027.17903736832508528637.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20220822220025.541691-1-luiz.dentz@gmail.com>
Hello:
This series was applied to bluetooth/bluez.git (master)
by Luiz Augusto von Dentz <luiz.von.dentz@intel.com>:
On Mon, 22 Aug 2022 15:00:24 -0700 you wrote:
> From: Luiz Augusto von Dentz <luiz.von.dentz@intel.com>
>
> This adds a destroy callback to bthost_add_iso_hook so its user can
> detect when the hook is freed when the connection is disconnected.
> ---
> emulator/bthost.c | 8 +++++++-
> emulator/bthost.h | 3 ++-
> tools/iso-tester.c | 2 +-
> 3 files changed, 10 insertions(+), 3 deletions(-)
Here is the summary with links:
- [BlueZ,1/2] bthost: Add destroy callback to bthost_add_iso_hook
https://git.kernel.org/pub/scm/bluetooth/bluez.git/?id=5bf220eb3b86
- [BlueZ,2/2] iso-tester: Make use of bthost_add_iso_hook destroy callback
https://git.kernel.org/pub/scm/bluetooth/bluez.git/?id=081897da74f0
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:[~2022-08-22 22:40 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-22 22:00 [PATCH BlueZ 1/2] bthost: Add destroy callback to bthost_add_iso_hook Luiz Augusto von Dentz
2022-08-22 22:00 ` [PATCH BlueZ 2/2] iso-tester: Make use of bthost_add_iso_hook destroy callback Luiz Augusto von Dentz
2022-08-22 22:27 ` [BlueZ,1/2] bthost: Add destroy callback to bthost_add_iso_hook bluez.test.bot
2022-08-22 22:40 ` 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=166120801512.10027.17903736832508528637.git-patchwork-notify@kernel.org \
--to=patchwork-bot+bluetooth@kernel.org \
--cc=linux-bluetooth@vger.kernel.org \
--cc=luiz.dentz@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.