From: patchwork-bot+bluetooth@kernel.org
To: Bastien Nocera <hadess@hadess.net>
Cc: linux-bluetooth@vger.kernel.org
Subject: Re: [PATCH BlueZ 0/2] Fix bluetoothctl no output
Date: Fri, 27 Feb 2026 15:20:04 +0000 [thread overview]
Message-ID: <177220560479.2588496.7908037575666693555.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260227112900.1946851-1-hadess@hadess.net>
Hello:
This series was applied to bluetooth/bluez.git (master)
by Luiz Augusto von Dentz <luiz.von.dentz@intel.com>:
On Fri, 27 Feb 2026 12:27:16 +0100 you wrote:
> This fixes a regression in 5.86, and works around a problem specific to
> btmgmt.
>
> Both commits can be tested independently using the regression test in
> the meson port:
> https://github.com/hadess/bluez/commits/wip/hadess/add-integration-tests/
>
> [...]
Here is the summary with links:
- [BlueZ,1/2] Revert "shared/shell: Don't init input for non-interactive shells"
https://git.kernel.org/pub/scm/bluetooth/bluez.git/?id=b33e923b55e4
- [BlueZ,2/2] tools: Work-around broken stdin handling in home-made mainloop
https://git.kernel.org/pub/scm/bluetooth/bluez.git/?id=21e13976f2e3
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:[~2026-02-27 15:20 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-27 11:27 [PATCH BlueZ 0/2] Fix bluetoothctl no output Bastien Nocera
2026-02-27 11:27 ` [PATCH BlueZ 1/2] Revert "shared/shell: Don't init input for non-interactive shells" Bastien Nocera
2026-02-27 12:40 ` Fix bluetoothctl no output bluez.test.bot
2026-02-27 11:27 ` [PATCH BlueZ 2/2] tools: Work-around broken stdin handling in home-made mainloop Bastien Nocera
2026-02-27 15:20 ` 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=177220560479.2588496.7908037575666693555.git-patchwork-notify@kernel.org \
--to=patchwork-bot+bluetooth@kernel.org \
--cc=hadess@hadess.net \
--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