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 v2 1/3] audio: transport: Fix crash on A2DP suspend
Date: Thu, 04 Jan 2024 16:10:26 +0000 [thread overview]
Message-ID: <170438462677.32236.8083382052140471903.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20240103205124.3839768-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 Wed, 3 Jan 2024 15:51:22 -0500 you wrote:
> From: Luiz Augusto von Dentz <luiz.von.dentz@intel.com>
>
> Commit 052534ae07b8 ("transport: Update transport release flow for
> bcast src") introduced a crash where it assumes transport->data always
> refers to struct bap_transport which causes a crash when the transport
> is in fact A2DP.
>
> [...]
Here is the summary with links:
- [BlueZ,v2,1/3] audio: transport: Fix crash on A2DP suspend
https://git.kernel.org/pub/scm/bluetooth/bluez.git/?id=36f057d7f66c
- [BlueZ,v2,2/3] audio/transport: Refactor transport operations
https://git.kernel.org/pub/scm/bluetooth/bluez.git/?id=e4764af76228
- [BlueZ,v2,3/3] audio/transport: Fix runtime error
https://git.kernel.org/pub/scm/bluetooth/bluez.git/?id=1c321baca781
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:[~2024-01-04 16:10 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-03 20:51 [PATCH BlueZ v2 1/3] audio: transport: Fix crash on A2DP suspend Luiz Augusto von Dentz
2024-01-03 20:51 ` [PATCH BlueZ v2 2/3] audio/transport: Refactor transport operations Luiz Augusto von Dentz
2024-01-03 20:51 ` [PATCH BlueZ v2 3/3] audio/transport: Fix runtime error Luiz Augusto von Dentz
2024-01-03 22:28 ` [BlueZ,v2,1/3] audio: transport: Fix crash on A2DP suspend bluez.test.bot
2024-01-04 16:10 ` 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=170438462677.32236.8083382052140471903.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.