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: [RFC PATCH] Bluetooth: btusb: Fix bluetooth on Intel Macbook 2014
From:   patchwork-bot+bluetooth@kernel.org
Message-Id: <168927902189.26469.5406966566822603728.git-patchwork-notify@kernel.org>
Date:   Thu, 13 Jul 2023 20:10:21 +0000
References: <20230713102514.699277-1-tomasz.mon@nordicsemi.no>
In-Reply-To: <20230713102514.699277-1-tomasz.mon@nordicsemi.no>
To:     =?utf-8?q?Tomasz_Mo=C5=84_=3Ctomasz=2Emon=40nordicsemi=2Eno=3E?=@ci.codeaurora.org
Cc:     linux-bluetooth@vger.kernel.org, luiz.dentz@gmail.com,
        johan.hedberg@gmail.com, marcel@holtmann.org,
        johnbholland@icloud.com, carles.cufi@nordicsemi.no,
        pmenzel@molgen.mpg.de
Precedence: bulk

Hello:

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

On Thu, 13 Jul 2023 12:25:14 +0200 you wrote:
> Commit c13380a55522 ("Bluetooth: btusb: Do not require hardcoded
> interface numbers") inadvertedly broke bluetooth on Intel Macbook 2014.
> The intention was to keep behavior intact when BTUSB_IFNUM_2 is set and
> otherwise allow any interface numbers. The problem is that the new logic
> condition omits the case where bInterfaceNumber is 0.
> 
> Fix BTUSB_IFNUM_2 handling by allowing both interface number 0 and 2
> when the flag is set.
> 
> [...]

Here is the summary with links:
  - [RFC] Bluetooth: btusb: Fix bluetooth on Intel Macbook 2014
    https://git.kernel.org/bluetooth/bluetooth-next/c/f0408f0a1998

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