Linux bluetooth development
 help / color / mirror / Atom feed
From: patchwork-bot+bluetooth@kernel.org
To: =?utf-8?b?RnLDqWTDqXJpYyBEYW5pcyA8ZnJlZGVyaWMuZGFuaXNAY29sbGFib3JhLmNvbT4=?=@aws-us-west-2-korg-oddjob-rhel9-1.codeaurora.org
Cc: linux-bluetooth@vger.kernel.org
Subject: Re: [PATCH BlueZ 1/7] plugins/admin: make AdminPolicy state per-adapter
Date: Wed, 15 Jul 2026 17:00:09 +0000	[thread overview]
Message-ID: <178413480939.415350.6266083914082860341.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260702083641.378994-1-frederic.danis@collabora.com>

Hello:

This series was applied to bluetooth/bluez.git (master)
by Luiz Augusto von Dentz <luiz.von.dentz@intel.com>:

On Thu,  2 Jul 2026 10:36:35 +0200 you wrote:
> Fix AdminPolicy D-Bus updates being emitted on the wrong adapter path
> by removing the single global policy context and moving to per-adapter
> policy objects.
> 
> Changes include:
> - track policy contexts in a policy queue keyed by adapter pointer
> - keep per-adapter device lists inside each policy context
> - emit ServiceAllowList changes using the callback's adapter context
> - scope device affected updates to the current adapter only
> - clean up probe/remove lifecycle so adapters are registered and torn
>   down independently
> - remove remaining global policy_data/devices coupling
> 
> [...]

Here is the summary with links:
  - [BlueZ,1/7] plugins/admin: make AdminPolicy state per-adapter
    (no matching commit)
  - [BlueZ,2/7] client/bluetoothctl: make admin.allow controller-aware
    (no matching commit)
  - [BlueZ,3/7] doc: document admin.allow optional controller argument
    (no matching commit)
  - [BlueZ,4/7] src/adapter: enforce allowlist for local services
    (no matching commit)
  - [BlueZ,5/7] plugins/admin: reapply allowlist on policy updates
    (no matching commit)
  - [BlueZ,6/7] doc: describe admin allowlist runtime enforcement
    (no matching commit)
  - [BlueZ,7/7] profiles/audio: fix UAF on external media service teardown
    https://git.kernel.org/pub/scm/bluetooth/bluez.git/?id=7482aceece70

You are awesome, thank you!
-- 
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html



      parent reply	other threads:[~2026-07-15 17:00 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-02  8:36 [PATCH BlueZ 1/7] plugins/admin: make AdminPolicy state per-adapter Frédéric Danis
2026-07-02  8:36 ` [PATCH BlueZ 2/7] client/bluetoothctl: make admin.allow controller-aware Frédéric Danis
2026-07-02  8:36 ` [PATCH BlueZ 3/7] doc: document admin.allow optional controller argument Frédéric Danis
2026-07-02  8:36 ` [PATCH BlueZ 4/7] src/adapter: enforce allowlist for local services Frédéric Danis
2026-07-02  8:36 ` [PATCH BlueZ 5/7] plugins/admin: reapply allowlist on policy updates Frédéric Danis
2026-07-02  8:36 ` [PATCH BlueZ 6/7] doc: describe admin allowlist runtime enforcement Frédéric Danis
2026-07-02  8:36 ` [PATCH BlueZ 7/7] profiles/audio: fix UAF on external media service teardown Frédéric Danis
2026-07-02 11:57 ` [BlueZ,1/7] plugins/admin: make AdminPolicy state per-adapter bluez.test.bot
2026-07-15 17:00 ` 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=178413480939.415350.6266083914082860341.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+bluetooth@kernel.org \
    --cc==?utf-8?b?RnLDqWTDqXJpYyBEYW5pcyA8ZnJlZGVyaWMuZGFuaXNAY29sbGFib3JhLmNvbT4=?=@aws-us-west-2-korg-oddjob-rhel9-1.codeaurora.org \
    --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