From: patchwork-bot+bluetooth@kernel.org
To: Szabolcs Sipos <labuwx@balfug.com>
Cc: linux-bluetooth@vger.kernel.org, marcel@holtmann.org,
johan.hedberg@gmail.com, luiz.dentz@gmail.com,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/2] Bluetooth: btusb: RTL8761BUV consistent naming
Date: Wed, 31 Aug 2022 23:10:16 +0000 [thread overview]
Message-ID: <166198741627.19908.15124677919927831058.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20220825224208.343700-1-labuwx@balfug.com>
Hello:
This series was applied to bluetooth/bluetooth-next.git (master)
by Luiz Augusto von Dentz <luiz.von.dentz@intel.com>:
On Fri, 26 Aug 2022 00:42:07 +0200 you wrote:
> Based on photos available from the FCC, all currently supported RTL8761B
> series USB dongles have the same chip: RTL8761BUV.
>
> rtl8761bu is often used to refer to this chip.
> rtl8761b sometimes refers to this chip, and other times to its
> UART variant (RTL8761BTV).
>
> [...]
Here is the summary with links:
- [1/2] Bluetooth: btusb: RTL8761BUV consistent naming
https://git.kernel.org/bluetooth/bluetooth-next/c/d8daa3991652
- [2/2] Bluetooth: btusb: Add RTL8761BUV device (Edimax BT-8500)
https://git.kernel.org/bluetooth/bluetooth-next/c/c7577014b74c
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:[~2022-08-31 23:10 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-25 22:42 [PATCH 1/2] Bluetooth: btusb: RTL8761BUV consistent naming Szabolcs Sipos
2022-08-25 22:42 ` [PATCH 2/2] Bluetooth: btusb: Add RTL8761BUV device (Edimax BT-8500) Szabolcs Sipos
2022-08-26 0:09 ` [1/2] Bluetooth: btusb: RTL8761BUV consistent naming bluez.test.bot
2022-08-31 23:10 ` 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=166198741627.19908.15124677919927831058.git-patchwork-notify@kernel.org \
--to=patchwork-bot+bluetooth@kernel.org \
--cc=johan.hedberg@gmail.com \
--cc=labuwx@balfug.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=linux-kernel@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox