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 v1 1/3] monitor: Fix instance where BN is printed as PTO
Date: Thu, 09 Oct 2025 19:40:06 +0000 [thread overview]
Message-ID: <176003880675.253496.15861307699859710689.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20251009162111.221677-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 Thu, 9 Oct 2025 12:21:09 -0400 you wrote:
> From: Luiz Augusto von Dentz <luiz.von.dentz@intel.com>
>
> This fixes 2 instance where BN is printed as PTO.
> ---
> monitor/packet.c | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
Here is the summary with links:
- [BlueZ,v1,1/3] monitor: Fix instance where BN is printed as PTO
https://git.kernel.org/pub/scm/bluetooth/bluez.git/?id=1067426bec48
- [BlueZ,v1,2/3] client/player: Fix prompting for bcode when one is already set
https://git.kernel.org/pub/scm/bluetooth/bluez.git/?id=411e3e0e4695
- [BlueZ,v1,3/3] bass: Fix restricting the BIS indexes to 1 as assistant
https://git.kernel.org/pub/scm/bluetooth/bluez.git/?id=4be24398f9ef
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:[~2025-10-09 19:40 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-09 16:21 [PATCH BlueZ v1 1/3] monitor: Fix instance where BN is printed as PTO Luiz Augusto von Dentz
2025-10-09 16:21 ` [PATCH BlueZ v1 2/3] client/player: Fix prompting for bcode when one is already set Luiz Augusto von Dentz
2025-10-09 16:21 ` [PATCH BlueZ v1 3/3] bass: Fix restricting the BIS indexes to 1 as assistant Luiz Augusto von Dentz
2025-10-09 17:44 ` [BlueZ,v1,1/3] monitor: Fix instance where BN is printed as PTO bluez.test.bot
2025-10-09 19: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=176003880675.253496.15861307699859710689.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox