From: fdanis-oss <noreply@github.com>
To: linux-bluetooth@vger.kernel.org
Subject: [bluez/bluez] 054e7e: client/btpclient: Move BTP definitions per service
Date: Mon, 23 Feb 2026 12:55:12 -0800 [thread overview]
Message-ID: <bluez/bluez/push/refs/heads/1056772/000000-054e7e@github.com> (raw)
Branch: refs/heads/1056772
Home: https://github.com/bluez/bluez
Commit: 054e7ead40b1341650a8ff86e45019609a9ac43a
https://github.com/bluez/bluez/commit/054e7ead40b1341650a8ff86e45019609a9ac43a
Author: Frédéric Danis <frederic.danis@collabora.com>
Date: 2026-02-23 (Mon, 23 Feb 2026)
Changed paths:
M Makefile.tools
A client/btpclient/btp/core.h
A client/btpclient/btp/gap.h
M client/btpclient/btpclient.c
M client/btpclient/btpclientctl.c
M client/btpclient/core.c
M client/btpclient/gap.c
A client/btpclient/services.h
M src/shared/btp.h
Log Message:
-----------
client/btpclient: Move BTP definitions per service
Over the years, BTP interface has grown way over what has been
initially anticipated in terms of number of services and commands.
To simplify addition and maintenance of new services this commit
split the commands in btp.h per services and move them under
client/btpclient/btp folder.
To unsubscribe from these emails, change your notification settings at https://github.com/bluez/bluez/settings/notifications
reply other threads:[~2026-02-23 20:55 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=bluez/bluez/push/refs/heads/1056772/000000-054e7e@github.com \
--to=noreply@github.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