From: Luiz Augusto von Dentz <noreply@github.com>
To: linux-bluetooth@vger.kernel.org
Subject: [bluez/bluez] d06b4a: device: Fix not auto-connecting profile
Date: Tue, 02 Aug 2022 13:23:10 -0700 [thread overview]
Message-ID: <bluez/bluez/push/refs/heads/master/cb4237-a65ddf@github.com> (raw)
Branch: refs/heads/master
Home: https://github.com/bluez/bluez
Commit: d06b4a6b74d4da0b997c981e1d506bf051f1a84d
https://github.com/bluez/bluez/commit/d06b4a6b74d4da0b997c981e1d506bf051f1a84d
Author: Luiz Augusto von Dentz <luiz.von.dentz@intel.com>
Date: 2022-08-01 (Mon, 01 Aug 2022)
Changed paths:
M src/device.c
Log Message:
-----------
device: Fix not auto-connecting profile
If the profile is registered and marked to auto-connect it shall
automatically be connected whenever a device is already connected.
Fixes: https://github.com/bluez/bluez/issues/370
Commit: 7adb3aa7efc3d70381c411c031f579ff63786994
https://github.com/bluez/bluez/commit/7adb3aa7efc3d70381c411c031f579ff63786994
Author: Luiz Augusto von Dentz <luiz.von.dentz@intel.com>
Date: 2022-08-02 (Tue, 02 Aug 2022)
Changed paths:
M src/adapter.c
M src/device.c
M src/device.h
M src/gatt-database.c
Log Message:
-----------
device: Add btd_ prefix to device_is_trusted
This adds btd_ prefix to device_is_trusted so it can be used by
plugins.
Commit: a65ddf710584f2b3dad04fb5e3d725ba340ea1ef
https://github.com/bluez/bluez/commit/a65ddf710584f2b3dad04fb5e3d725ba340ea1ef
Author: Luiz Augusto von Dentz <luiz.von.dentz@intel.com>
Date: 2022-08-02 (Tue, 02 Aug 2022)
Changed paths:
M plugins/sixaxis.c
M src/device.c
M src/device.h
Log Message:
-----------
sixaxis: Fix fliping device.trusted automatically
device.trusted is a user preference which controls if the devices needs
to be authorized or not so the plugin shall not overwrite it and instead
just honor what user has set and skip authorizing if already trusted.
Fixes: https://github.com/bluez/bluez/issues/372
Compare: https://github.com/bluez/bluez/compare/cb42377ae002...a65ddf710584
reply other threads:[~2022-08-02 20:23 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/master/cb4237-a65ddf@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.