Received-SPF: pass (google.com: domain of linux-bluetooth-owner@vger.kernel.org designates 2620:137:e000::3:6 as permitted sender) client-ip=2620:137:e000::3:6;
Content-Type: text/plain; charset="utf-8"
MIME-Version: 1.0
Content-Transfer-Encoding: 8bit
Subject: Re: [PATCH BlueZ] device: Fix not handling initiator properly
From:   patchwork-bot+bluetooth@kernel.org
Message-Id: <169454462657.13260.14879403068503955588.git-patchwork-notify@kernel.org>
Date:   Tue, 12 Sep 2023 18:50:26 +0000
References: <20230911223355.2701293-1-luiz.dentz@gmail.com>
In-Reply-To: <20230911223355.2701293-1-luiz.dentz@gmail.com>
To:     Luiz Augusto von Dentz <luiz.dentz@gmail.com>
Cc:     linux-bluetooth@vger.kernel.org
Precedence: bulk

Hello:

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

On Mon, 11 Sep 2023 15:33:55 -0700 you wrote:
> From: Luiz Augusto von Dentz <luiz.von.dentz@intel.com>
> 
> Previously initiator would be set whenever a central key was found
> which turns out to be unreliable besides the MGMT New Connection event
> does in fact inform if the connection was initiated locally or not.
> 
> Fixes: https://github.com/bluez/bluez/issues/598
> 
> [...]

Here is the summary with links:
  - [BlueZ] device: Fix not handling initiator properly
    https://git.kernel.org/pub/scm/bluetooth/bluez.git/?id=2d2389d96702

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