Linux bluetooth development
 help / color / mirror / Atom feed
From: "github-actions[bot]" <noreply@github.com>
To: linux-bluetooth@vger.kernel.org
Subject: [bluez/bluez] 9fc9cb: org.bluez.Device: Add Role property
Date: Thu, 08 Oct 2026 09:55:40 -0700	[thread overview]
Message-ID: <bluez/bluez/push/refs/heads/1181653/000000-2d7977@github.com> (raw)

  Branch: refs/heads/1181653
  Home:   https://github.com/bluez/bluez
  Commit: 9fc9cb887477044ac90162170b1f031d598f3d7d
      https://github.com/bluez/bluez/commit/9fc9cb887477044ac90162170b1f031d598f3d7d
  Author: Kevin Dewald <kevin@simpleble.org>
  Date:   2026-10-08 (Thu, 08 Oct 2026)

  Changed paths:
    M doc/org.bluez.Device.rst

  Log Message:
  -----------
  org.bluez.Device: Add Role property

This adds Role property which indicates whether the remote device is
the central or the peripheral of the current LE connection, so
applications can tell a central that connected to the adapter from a
peripheral the adapter connected to.

Assisted-by: Claude:claude-opus-5.5


  Commit: f447eeb2dd2fe46a98239cea8bc3fce0a10b0ae7
      https://github.com/bluez/bluez/commit/f447eeb2dd2fe46a98239cea8bc3fce0a10b0ae7
  Author: Kevin Dewald <kevin@simpleble.org>
  Date:   2026-10-08 (Thu, 08 Oct 2026)

  Changed paths:
    M src/device.c

  Log Message:
  -----------
  device: Add Role property

This implements Role property using the initiator flag of the Device
Connected event, which the kernel sets when the adapter created the
connection as central, and emits PropertiesChanged when an LE
connection is added or removed.

Assisted-by: Claude:claude-opus-5.5


  Commit: 2d79772deecd82f3139f01e248148e56ae4ea340
      https://github.com/bluez/bluez/commit/2d79772deecd82f3139f01e248148e56ae4ea340
  Author: Kevin Dewald <kevin@simpleble.org>
  Date:   2026-10-08 (Thu, 08 Oct 2026)

  Changed paths:
    M client/main.c

  Log Message:
  -----------
  client: Print Role in info

This prints the Role property with the likes of info command:

bluetoothctl> info <addr>
...
        Connected: yes
        Role: central

Assisted-by: Claude:claude-opus-5.5


Compare: https://github.com/bluez/bluez/compare/9fc9cb887477%5E...2d79772deecd

To unsubscribe from these emails, change your notification settings at https://github.com/bluez/bluez/settings/notifications

                 reply	other threads:[~2026-10-08 16: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/1181653/000000-2d7977@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