From: patchwork-bot+bluetooth@kernel.org
To: Kaihsin Chung <kaihsin.chung@synaptics.corp-partner.google.com>
Cc: linux-bluetooth@vger.kernel.org, marcel@holtmann.org,
luiz.dentz@gmail.com, robh@kernel.org, krzk+dt@kernel.org,
conor+dt@kernel.org, linusw@kernel.org,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
kaihsin.chung@synaptics.com
Subject: Re: [PATCH 0/2] Add support for the Synaptics BCM4384 Bluetooth controller.
Date: Fri, 04 Sep 2026 16:56:16 +0000 [thread overview]
Message-ID: <178854097613.344939.278042329764425597.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260817095550.648774-1-kaihsin.chung@synaptics.com>
Hello:
This series was applied to bluetooth/bluetooth-next.git (master)
by Luiz Augusto von Dentz <luiz.von.dentz@intel.com>:
On Mon, 17 Aug 2026 17:55:48 +0800 you wrote:
> The first patch adds the BCM4384 Device Tree compatible string.
> The second patch adds the controller support to the Broadcom
> Bluetooth driver
>
> Kaihsin Chung (2):
> dt-bindings: net: bluetooth: add BCM4384
> Bluetooth: btbcm: Add Synaptics 4384 chip support
>
> [...]
Here is the summary with links:
- [1/2] dt-bindings: net: bluetooth: add BCM4384
https://git.kernel.org/bluetooth/bluetooth-next/c/29d82dcf7273
- [2/2] Bluetooth: btbcm: Add Synaptics 4384 chip support
https://git.kernel.org/bluetooth/bluetooth-next/c/9aa9447804c7
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:[~2026-09-04 16:57 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-17 9:55 Kaihsin Chung
2026-08-17 9:55 ` [PATCH 1/2] dt-bindings: net: bluetooth: add BCM4384 Kaihsin Chung
2026-08-17 12:01 ` Linus Walleij
2026-08-18 9:19 ` Krzysztof Kozlowski
2026-08-17 9:55 ` [PATCH 2/2] Bluetooth: btbcm: Add Synaptics 4384 chip support Kaihsin Chung
2026-08-17 10:45 ` Paul Menzel
2026-09-04 16:56 ` 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=178854097613.344939.278042329764425597.git-patchwork-notify@kernel.org \
--to=patchwork-bot+bluetooth@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=kaihsin.chung@synaptics.com \
--cc=kaihsin.chung@synaptics.corp-partner.google.com \
--cc=krzk+dt@kernel.org \
--cc=linusw@kernel.org \
--cc=linux-bluetooth@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luiz.dentz@gmail.com \
--cc=marcel@holtmann.org \
--cc=robh@kernel.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
all inboxes | Powered by JetHome®