From: patchwork-bot+bluetooth@kernel.org
To: Christian Eggers <ceggers@arri.de>
Cc: linux-bluetooth@vger.kernel.org
Subject: Re: [PATCH Bluez v2 0/4] client: align 'io-cap' and 'pair' cmds with the docs
Date: Fri, 27 Feb 2026 15:20:06 +0000 [thread overview]
Message-ID: <177220560603.2588496.14899151545224229601.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260227143242.5204-1-ceggers@arri.de>
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 15:24:21 +0100 you wrote:
> According to doc/bluetoothctl-mgmt.rst, the 'io-cap' and 'pair' cmds
> should have a string type <cap> argument. But in the current
> implementation, the parser expects an integer (and doesn't complain if
> something else is passed).
>
> v2:
> - Split the first patch into two parts
> - Use an enum instead of preprocessor defines
> - Remove obsolete documentation update for l2test's -O <mtu> option
Here is the summary with links:
- [BlueZ,1/4] shared/mgmt: Add mgmt_parse_io_capability
https://git.kernel.org/pub/scm/bluetooth/bluez.git/?id=61f25f9aacdc
- [BlueZ,2/4] adapter/agent/device: migrate to shared enum/parser for IO capabilities
https://git.kernel.org/pub/scm/bluetooth/bluez.git/?id=47a1be34629f
- [BlueZ,3/4] client/mgmt: align implementation cmd_io_cap with its documentation
https://git.kernel.org/pub/scm/bluetooth/bluez.git/?id=63b82054c344
- [BlueZ,4/4] client/mgmt: align implementation cmd_pair with its documentation
https://git.kernel.org/pub/scm/bluetooth/bluez.git/?id=65fcbe05dce1
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: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-27 14:24 [PATCH Bluez v2 0/4] client: align 'io-cap' and 'pair' cmds with the docs Christian Eggers
2026-02-27 14:24 ` [PATCH BlueZ 1/4] shared/mgmt: Add mgmt_parse_io_capability Christian Eggers
2026-02-27 15:39 ` client: align 'io-cap' and 'pair' cmds with the docs bluez.test.bot
2026-02-27 14:24 ` [PATCH BlueZ 2/4] adapter/agent/device: migrate to shared enum/parser for IO capabilities Christian Eggers
2026-02-27 14:24 ` [PATCH BlueZ 3/4] client/mgmt: align implementation cmd_io_cap with its documentation Christian Eggers
2026-02-27 14:24 ` [PATCH BlueZ 4/4] client/mgmt: align implementation cmd_pair " Christian Eggers
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=177220560603.2588496.14899151545224229601.git-patchwork-notify@kernel.org \
--to=patchwork-bot+bluetooth@kernel.org \
--cc=ceggers@arri.de \
--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