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 v6 0/3] obexd: unregister profiles when the user is inactive
Date: Thu, 01 May 2025 13:50:32 +0000 [thread overview]
Message-ID: <174610743298.2986402.2691498734604978766.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20250430131648.1291354-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 Wed, 30 Apr 2025 14:13:59 +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,v6,1/3] obexd: Unregister profiles when the user is inactive
https://git.kernel.org/pub/scm/bluetooth/bluez.git/?id=765356e80262
- [BlueZ,v6,2/3] obexd: Support sd_login_monitor_get_timeout()
https://git.kernel.org/pub/scm/bluetooth/bluez.git/?id=8b29b5a46cdc
- [BlueZ,v6,3/3] Revert "obexd: only run one instance at once"
https://git.kernel.org/pub/scm/bluetooth/bluez.git/?id=f8d0dc114036
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-05-01 13:49 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-30 13:13 [PATCH BlueZ v6 0/3] obexd: unregister profiles when the user is inactive Andrew Sayers
2025-04-30 13:14 ` [PATCH BlueZ v6 1/3] obexd: Unregister " Andrew Sayers
2025-04-30 14:58 ` obexd: unregister " bluez.test.bot
2025-05-22 14:55 ` [PATCH BlueZ v6 1/3] obexd: Unregister " Frédéric Danis
2025-05-23 10:33 ` Andrew Sayers
2025-05-23 11:17 ` Frédéric Danis
2025-05-23 16:31 ` Andrew Sayers
2025-05-23 17:27 ` Frédéric Danis
2025-05-26 9:07 ` Andrew Sayers
2025-04-30 13:14 ` [PATCH BlueZ v6 2/3] obexd: Support sd_login_monitor_get_timeout() Andrew Sayers
2025-04-30 13:14 ` [PATCH BlueZ v6 3/3] Revert "obexd: only run one instance at once" Andrew Sayers
2025-05-01 13:50 ` 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=174610743298.2986402.2691498734604978766.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