From: "Šimon Mikuda" <noreply@github.com>
To: linux-bluetooth@vger.kernel.org
Subject: [bluez/bluez] 51f28d: device: Refactor device_discover_services function
Date: Mon, 08 Jun 2026 04:29:29 -0700 [thread overview]
Message-ID: <bluez/bluez/push/refs/heads/1107774/000000-fa023b@github.com> (raw)
Branch: refs/heads/1107774
Home: https://github.com/bluez/bluez
Commit: 51f28d24f7c767616f5101050789e67a25789a5e
https://github.com/bluez/bluez/commit/51f28d24f7c767616f5101050789e67a25789a5e
Author: Simon Mikuda <simon.mikuda@streamunlimited.com>
Date: 2026-06-08 (Mon, 08 Jun 2026)
Changed paths:
M profiles/input/server.c
M src/adapter.c
M src/device.c
M src/device.h
Log Message:
-----------
device: Refactor device_discover_services function
After refactoring we can reuse function once more in function
void device_bonding_complete(...)
Commit: 0967651164a2118729967a25d670eb3f249aa72f
https://github.com/bluez/bluez/commit/0967651164a2118729967a25d670eb3f249aa72f
Author: Simon Mikuda <simon.mikuda@streamunlimited.com>
Date: 2026-06-08 (Mon, 08 Jun 2026)
Changed paths:
M src/device.c
Log Message:
-----------
device: Rename start_discovery function
Rename it to start_discovery_cb to indicate that it is callback function
from timer.
Commit: fa023bc6417933847b1fcea23cb0da75fcc31eed
https://github.com/bluez/bluez/commit/fa023bc6417933847b1fcea23cb0da75fcc31eed
Author: Simon Mikuda <simon.mikuda@streamunlimited.com>
Date: 2026-06-08 (Mon, 08 Jun 2026)
Changed paths:
M src/device.c
Log Message:
-----------
device: Fix returning discovery error for Device.Pair
If discovery was requesed from pair request we will report successfull
pairing even if there was an error during discovery.
Compare: https://github.com/bluez/bluez/compare/51f28d24f7c7%5E...fa023bc64179
To unsubscribe from these emails, change your notification settings at https://github.com/bluez/bluez/settings/notifications
reply other threads:[~2026-06-08 11:29 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/1107774/000000-fa023b@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