Content-Type: text/plain; charset="utf-8"
MIME-Version: 1.0
Content-Transfer-Encoding: 8bit
Subject: Re: [PATCH] Bluetooth: btusb: Do not require hardcoded interface numbers
From:   patchwork-bot+bluetooth@kernel.org
Message-Id: <167640721693.14815.1829404547628242837.git-patchwork-notify@kernel.org>
Date:   Tue, 14 Feb 2023 20:40:16 +0000
References: <20230207115741.122854-1-tomasz.mon@nordicsemi.no>
In-Reply-To: <20230207115741.122854-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, marcel@holtmann.org,
        johan.hedberg@gmail.com, luiz.dentz@gmail.com,
        carles.cufi@nordicsemi.no
Precedence: bulk

Hello:

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

On Tue, 7 Feb 2023 12:57:41 +0100 you wrote:
> Remove hardcoded interface number check because Bluetooth specification
> since version 4.0 only recommends and no longer requires specific
> interface numbers.
> 
> While earlier Bluetooth versions, i.e. 2.1 + EDR and 3.0 + HS, contain
> required configuration table in Volume 4 - Host Controller Interface
> Part B - USB Transport Layer, Bluetooth Core Specification Addendum 2
> changes the table from required to recommended configuration.
> 
> [...]

Here is the summary with links:
  - Bluetooth: btusb: Do not require hardcoded interface numbers
    https://git.kernel.org/bluetooth/bluetooth-next/c/dbf27f4a6adb

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