From: patchwork-bot+bluetooth@kernel.org
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
Subject: Re: [PATCH] Bluetooth: btusb: Do not require hardcoded interface numbers
Date: Tue, 14 Feb 2023 20:40:16 +0000 [thread overview]
Message-ID: <167640721693.14815.1829404547628242837.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20230207115741.122854-1-tomasz.mon@nordicsemi.no>
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
prev parent reply other threads:[~2023-02-14 20:40 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-07 11:57 [PATCH] Bluetooth: btusb: Do not require hardcoded interface numbers Tomasz Moń
2023-02-07 12:42 ` bluez.test.bot
2023-02-09 21:32 ` [PATCH] " Luiz Augusto von Dentz
2023-02-10 6:31 ` Tomasz Moń
2023-02-14 20:40 ` 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=167640721693.14815.1829404547628242837.git-patchwork-notify@kernel.org \
--to=patchwork-bot+bluetooth@kernel.org \
--cc==?utf-8?q?Tomasz_Mo=C5=84_=3Ctomasz=2Emon=40nordicsemi=2Eno=3E?=@ci.codeaurora.org \
--cc=carles.cufi@nordicsemi.no \
--cc=johan.hedberg@gmail.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=luiz.dentz@gmail.com \
--cc=marcel@holtmann.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.