From: patchwork-bot+bluetooth@kernel.org
To: Andrew Sayers <kernel.org@pileofstuff.org>
Cc: linux-bluetooth@vger.kernel.org, luiz.dentz@gmail.com, pav@iki.fi
Subject: Re: [PATCH BlueZ v5 0/6] obexd: unregister profiles when the user is inactive
Date: Tue, 29 Apr 2025 18:10:27 +0000 [thread overview]
Message-ID: <174595022774.1757079.8232614301525449852.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20250429141533.803295-1-kernel.org@pileofstuff.org>
Hello:
This series was applied to bluetooth/bluez.git (master)
by Luiz Augusto von Dentz <luiz.von.dentz@intel.com>:
On Tue, 29 Apr 2025 15:14:10 +0100 you wrote:
> This is a follow-up to "obexd: only run one instance at once".
> Instead of refusing to run parallel services, it unregisters
> profiles when the user is inactive. This avoids the need
> for tmpfiles, and avoids issues where the user with the
> obex service logs out, leaving obex disabled altogether.
>
> Luiz previously suggested moving this to systemd, but I haven't had much
> luck getting the systemd devs to accept changes, and Pauli's mention of
> elogind (i.e. logind without systemd) suggests it's probably better
> to avoid the dependency anyway.
>
> [...]
Here is the summary with links:
- [BlueZ,v5,1/6] pbap: Support calling pbap_init() after pbap_exit()
https://git.kernel.org/pub/scm/bluetooth/bluez.git/?id=9bf6bb654ff7
- [BlueZ,v5,2/6] obexd/bluetooth: Support calling bluetooth_init() after bluetooth_exit()
https://git.kernel.org/pub/scm/bluetooth/bluez.git/?id=29f3c07b8dc9
- [BlueZ,v5,3/6] obexd: Support creating private system/session bus connections
https://git.kernel.org/pub/scm/bluetooth/bluez.git/?id=237d818ef294
- [BlueZ,v5,4/6] obexd: Unregister profiles when the user is inactive
(no matching commit)
- [BlueZ,v5,5/6] obexd: Support sd_login_monitor_get_timeout()
(no matching commit)
- [BlueZ,v5,6/6] Revert "obexd: only run one instance at once"
(no matching commit)
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-04-29 18:09 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-29 14:14 [PATCH BlueZ v5 0/6] obexd: unregister profiles when the user is inactive Andrew Sayers
2025-04-29 14:14 ` [PATCH BlueZ v5 1/6] pbap: Support calling pbap_init() after pbap_exit() Andrew Sayers
2025-04-29 15:51 ` obexd: unregister profiles when the user is inactive bluez.test.bot
2025-04-29 14:14 ` [PATCH BlueZ v5 2/6] obexd/bluetooth: Support calling bluetooth_init() after bluetooth_exit() Andrew Sayers
2025-04-29 14:14 ` [PATCH BlueZ v5 3/6] obexd: Support creating private system/session bus connections Andrew Sayers
2025-04-29 14:14 ` [PATCH BlueZ v5 4/6] obexd: Unregister profiles when the user is inactive Andrew Sayers
2025-04-29 17:25 ` Luiz Augusto von Dentz
2025-04-29 19:20 ` Andrew Sayers
2025-04-29 21:12 ` Luiz Augusto von Dentz
2025-04-29 14:14 ` [PATCH BlueZ v5 5/6] obexd: Support sd_login_monitor_get_timeout() Andrew Sayers
2025-04-29 14:14 ` [PATCH BlueZ v5 6/6] Revert "obexd: only run one instance at once" Andrew Sayers
2025-04-29 18:10 ` 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=174595022774.1757079.8232614301525449852.git-patchwork-notify@kernel.org \
--to=patchwork-bot+bluetooth@kernel.org \
--cc=kernel.org@pileofstuff.org \
--cc=linux-bluetooth@vger.kernel.org \
--cc=luiz.dentz@gmail.com \
--cc=pav@iki.fi \
/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