From: Krzysztof Kozlowski <krzk@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 <kaihsin.chung@synaptics.com>
Subject: Re: [PATCH 1/2] dt-bindings: net: bluetooth: add BCM4384
Date: Tue, 18 Aug 2026 11:19:31 +0200 [thread overview]
Message-ID: <20260818-warping-magic-leopard-f5ee10@quoll> (raw)
In-Reply-To: <20260817095550.648774-2-kaihsin.chung@synaptics.com>
On Mon, Aug 17, 2026 at 05:55:49PM +0800, Kaihsin Chung wrote:
> Add the brcm,bcm4384-bt compatible string to support the
> Synaptics BCM4384 Bluetooth controller.
>
> Signed-off-by: Kaihsin Chung <kaihsin.chung@synaptics.com>
> ---
> .../devicetree/bindings/net/bluetooth/brcm,bluetooth.yaml | 1 +
> 1 file changed, 1 insertion(+)
How many duplicates of this are we going to get?
Best regards,
Krzysztof
next prev parent reply other threads:[~2026-08-18 9:19 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-17 9:55 [PATCH 0/2] Add support for the Synaptics BCM4384 Bluetooth controller 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 [this message]
2026-08-17 9:55 ` [PATCH 2/2] Bluetooth: btbcm: Add Synaptics 4384 chip support Kaihsin Chung
2026-08-17 10:45 ` Paul Menzel
-- strict thread matches above, loose matches on Subject: below --
2026-08-17 9:27 [PATCH 0/2] Bluetooth: add Synaptics BCM4384 support kaihsin
2026-08-17 9:27 ` [PATCH 1/2] dt-bindings: net: bluetooth: add BCM4384 kaihsin
2026-08-18 9:17 ` Krzysztof Kozlowski
2026-08-18 9:20 ` Krzysztof Kozlowski
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=20260818-warping-magic-leopard-f5ee10@quoll \
--to=krzk@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