From: Krzysztof Kozlowski <krzk@kernel.org>
To: kaihsin <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 <kaihsin.chung@synaptics.com>
Subject: Re: [PATCH 1/2] dt-bindings: net: bluetooth: add BCM4384
Date: Tue, 18 Aug 2026 11:20:12 +0200 [thread overview]
Message-ID: <22c4f36d-617a-4dc0-8db8-c9bc4785c09a@kernel.org> (raw)
In-Reply-To: <20260818-humble-shellfish-of-vigor-79a10d@quoll>
On 18/08/2026 11:17, Krzysztof Kozlowski wrote:
> On Mon, Aug 17, 2026 at 05:27:22PM +0800, kaihsin wrote:
>> Add the brcm,bcm4384-bt compatible string to support the
>> Synaptics BCM4384 Bluetooth controller.
>>
>> Signed-off-by: kaihsin <kaihsin.chung@synaptics.com>
>
> Looks incomplete DCO, at least judging by email address.
>
>> ---
Heh, not only incomplete but incorrect - does not match the author.
Best regards,
Krzysztof
next prev parent reply other threads:[~2026-08-18 9:20 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
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-17 10:44 ` Bluetooth: add Synaptics BCM4384 support bluez.test.bot
2026-08-18 9:17 ` [PATCH 1/2] dt-bindings: net: bluetooth: add BCM4384 Krzysztof Kozlowski
2026-08-18 9:20 ` Krzysztof Kozlowski [this message]
2026-08-17 9:27 ` [PATCH 2/2] Bluetooth: btbcm: Add Synaptics 4384 chip support Add support for the Synaptics 4384 Bluetooth controller by adding the corresponding chip IDs kaihsin
2026-08-17 9:36 ` Paul Menzel
2026-08-17 12:00 ` Linus Walleij
-- strict thread matches above, loose matches on Subject: below --
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
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=22c4f36d-617a-4dc0-8db8-c9bc4785c09a@kernel.org \
--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 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.