From: patchwork-bot+bluetooth@kernel.org
To: Pauli Virtanen <pav@iki.fi>
Cc: linux-bluetooth@vger.kernel.org
Subject: Re: [PATCH BlueZ v2 1/3] audio/transport: add media_transport_get_stream method for transports
Date: Thu, 16 Feb 2023 00:51:06 +0000 [thread overview]
Message-ID: <167650866660.21680.8123172316646752195.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <f973ae1e4b2c07902f98a6e7776b44bef25670be.1676499415.git.pav@iki.fi>
Hello:
This series was applied to bluetooth/bluez.git (master)
by Luiz Augusto von Dentz <luiz.von.dentz@intel.com>:
On Wed, 15 Feb 2023 22:26:00 +0000 you wrote:
> Add a method for getting the audio stream associated with a media
> transport.
> ---
>
> Notes:
> v2: make generic and split out to separate patch
>
> [...]
Here is the summary with links:
- [BlueZ,v2,1/3] audio/transport: add media_transport_get_stream method for transports
https://git.kernel.org/pub/scm/bluetooth/bluez.git/?id=f7d0599afe9b
- [BlueZ,v2,2/3] media: look up BAP transports by their associated stream
https://git.kernel.org/pub/scm/bluetooth/bluez.git/?id=e9163b09a3df
- [BlueZ,v2,3/3] media: fix ASAN crash in pac_config_cb
https://git.kernel.org/pub/scm/bluetooth/bluez.git/?id=5d347b54714e
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:[~2023-02-16 0:51 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-15 22:26 [PATCH BlueZ v2 1/3] audio/transport: add media_transport_get_stream method for transports Pauli Virtanen
2023-02-15 22:26 ` [PATCH BlueZ v2 2/3] media: look up BAP transports by their associated stream Pauli Virtanen
2023-02-15 22:26 ` [PATCH BlueZ v2 3/3] media: fix ASAN crash in pac_config_cb Pauli Virtanen
2023-02-15 23:52 ` [BlueZ,v2,1/3] audio/transport: add media_transport_get_stream method for transports bluez.test.bot
2023-02-16 0:51 ` 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=167650866660.21680.8123172316646752195.git-patchwork-notify@kernel.org \
--to=patchwork-bot+bluetooth@kernel.org \
--cc=linux-bluetooth@vger.kernel.org \
--cc=pav@iki.fi \
/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;
as well as URLs for NNTP newsgroup(s).