From: patchwork-bot+bluetooth@kernel.org
To: Arkadiusz Bokowy <arkadiusz.bokowy@gmail.com>
Cc: linux-bluetooth@vger.kernel.org
Subject: Re: [PATCH BlueZ 1/2] uuid-helper: Accept any 16-bit HEX value as a valid UUID
Date: Mon, 03 Mar 2025 17:50:38 +0000 [thread overview]
Message-ID: <174102423824.3666733.13768128595760430757.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20250302090331.17756-1-arkadiusz.bokowy@gmail.com>
Hello:
This series was applied to bluetooth/bluez.git (master)
by Luiz Augusto von Dentz <luiz.von.dentz@intel.com>:
On Sun, 2 Mar 2025 10:03:30 +0100 you wrote:
> The bt_name2string() function restricts HEX values to the list of
> predefined service names. This list is very limited, so loosing that
> restriction will allow to pass any 16-bit HEX value as a profile to
> D-Bus API calls like ConnectProfile or RegisterProfile.
> ---
> src/uuid-helper.c | 11 +++++------
> 1 file changed, 5 insertions(+), 6 deletions(-)
Here is the summary with links:
- [BlueZ,1/2] uuid-helper: Accept any 16-bit HEX value as a valid UUID
(no matching commit)
- [BlueZ,2/2] core: Report error in case of bt_name2string failure
https://git.kernel.org/pub/scm/bluetooth/bluez.git/?id=32e2e5a42b2b
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-03-03 17:50 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-02 9:03 [PATCH BlueZ 1/2] uuid-helper: Accept any 16-bit HEX value as a valid UUID Arkadiusz Bokowy
2025-03-02 9:03 ` [PATCH BlueZ 2/2] core: Report error in case of bt_name2string failure Arkadiusz Bokowy
2025-03-02 9:41 ` [BlueZ,1/2] uuid-helper: Accept any 16-bit HEX value as a valid UUID bluez.test.bot
2025-03-03 17:50 ` 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=174102423824.3666733.13768128595760430757.git-patchwork-notify@kernel.org \
--to=patchwork-bot+bluetooth@kernel.org \
--cc=arkadiusz.bokowy@gmail.com \
--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