Received-SPF: pass (google.com: domain of linux-bluetooth-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20;
Content-Type: text/plain; charset="utf-8"
MIME-Version: 1.0
Content-Transfer-Encoding: 8bit
Subject: Re: [PATCH] Bluetooth: hci_conn: Fix CIS connection dst_type handling
From:   patchwork-bot+bluetooth@kernel.org
Message-Id: <166552141698.15349.13183520200083892484.git-patchwork-notify@kernel.org>
Date:   Tue, 11 Oct 2022 20:50:16 +0000
References: <20221009174216.17533-1-pav@iki.fi>
In-Reply-To: <20221009174216.17533-1-pav@iki.fi>
To:     Pauli Virtanen <pav@iki.fi>
Cc:     linux-bluetooth@vger.kernel.org
Precedence: bulk

Hello:

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

On Sun,  9 Oct 2022 20:42:15 +0300 you wrote:
> hci_connect_cis and iso_connect_cis call hci_bind_cis inconsistently
> with dst_type being either ISO socket address type or the HCI type, but
> these values cannot be mixed like this. Fix this by using only the
> socket address type.
> 
> CIS connection dst_type was also not initialized in hci_bind_cis, even
> though it is used in hci_conn_hash_lookup_cis to find existing
> connections.  Set the value in hci_bind_cis, so that existing CIS
> connections are found e.g. when doing deferred socket connections, also
> when dst_type is not 0 (ADDR_LE_DEV_PUBLIC).
> 
> [...]

Here is the summary with links:
  - Bluetooth: hci_conn: Fix CIS connection dst_type handling
    (no matching commit)
  - [v2,2/2] Bluetooth: hci_conn: use HCI dst_type values also for BIS
    https://git.kernel.org/bluetooth/bluetooth-next/c/4d12cd187c82

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