From: Krzysztof Kozlowski <krzk@kernel.org>
To: kaihsin Chung <kaihsin.chung@synaptics.corp-partner.google.com>,
linux-bluetooth@vger.kernel.org
Cc: marcel@holtmann.org, luiz.von.dentz@intel.com,
linux-kernel@vger.kernel.org,
Kaihsin Chung <kaihsin.chung@synaptics.com>
Subject: Re: [PATCH v6 1/2] dt-bindings: net: bluetooth: Add brcm,bcm4384-bt
Date: Wed, 20 May 2026 13:19:26 +0200 [thread overview]
Message-ID: <db9eceed-c136-4d5a-a0a2-5fadf2ab000c@kernel.org> (raw)
In-Reply-To: <20260520090131.3505676-2-kaihsin.chung@synaptics.com>
On 20/05/2026 11:01, kaihsin Chung wrote:
> From: Kaihsin Chung <kaihsin.chung@synaptics.com>
>
> Add the compatible string for the Broadcom BCM4384
> Bluetooth controller.
Please use scripts/get_maintainers.pl to get a list of necessary people
and lists to CC. It might happen, that command when run on an older
kernel, gives you outdated entries. Therefore please be sure you base
your patches on recent Linux kernel.
Tools like b4 or scripts/get_maintainer.pl provide you proper list of
people, so fix your workflow. Tools might also fail if you work on some
ancient tree (don't, instead use mainline) or work on fork of kernel
(don't, instead use mainline). Just use b4 and everything should be
fine, although remember about `b4 prep --auto-to-cc` if you added new
patches to the patchset.
You missed at least devicetree list (maybe more), so this won't be
tested by automated tooling. Performing review on untested code might be
a waste of time.
Please kindly resend and include all necessary To/Cc entries.
Please wrap commit message according to Linux coding style / submission
process (neither too early nor over the limit):
https://elixir.bootlin.com/linux/v6.4-rc1/source/Documentation/process/submitting-patches.rst#L597
Do not attach (thread) your patchsets to some other threads (unrelated
or older versions). This buries them deep in the mailbox and might
interfere with applying entire sets. See also:
https://elixir.bootlin.com/linux/v6.16-rc2/source/Documentation/process/submitting-patches.rst#L830
>
> Signed-off-by: Kaihsin Chung <kaihsin.chung@synaptics.com>
> ---
> .../bindings/net/bluetooth/brcm,bcm4377-bluetooth.yaml | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/Documentation/devicetree/bindings/net/bluetooth/brcm,bcm4377-bluetooth.yaml b/Documentation/devicetree/bindings/net/bluetooth/brcm,bcm4377-bluetooth.yaml
> index 37cb39a3a62e..139d9b47329c 100644
> --- a/Documentation/devicetree/bindings/net/bluetooth/brcm,bcm4377-bluetooth.yaml
> +++ b/Documentation/devicetree/bindings/net/bluetooth/brcm,bcm4377-bluetooth.yaml
> @@ -23,7 +23,7 @@ properties:
> - pci14e4,5fa0 # BCM4377
> - pci14e4,5f69 # BCM4378
> - pci14e4,5f71 # BCM4387
> -
Why?
> + - brcm,bcm4384-bt
> reg:
> maxItems: 1
>
I really doubt you tested it. What sort of bus is used for your device?
Best regards,
Krzysztof
next prev parent reply other threads:[~2026-05-20 11:19 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-08 8:32 [PATCH] Bluetooth: Add Synaptcis 4384 Chip Support kaihsin
2026-04-08 8:46 ` Paul Menzel
2026-04-08 14:46 ` Luiz Augusto von Dentz
2026-04-08 9:21 ` [PATCH v2] Bluetooth: Add Synaptics " kaihsin Chung
2026-04-08 10:31 ` [v2] " bluez.test.bot
2026-04-08 9:21 ` Bluetooth: Add Synaptcis " bluez.test.bot
2026-04-09 1:30 ` [PATCH v3] Bluetooth: Add Synaptics " kaihsin Chung
2026-04-09 20:19 ` [v3] " bluez.test.bot
2026-04-10 14:16 ` Luiz Augusto von Dentz
2026-04-29 9:32 ` Kaihsin Chung
2026-04-09 20:20 ` Bluetooth: Add Synaptcis " bluez.test.bot
2026-05-13 2:20 ` [PATCH v4] Bluetooth: Add Synaptics " kaihsin Chung
2026-05-13 4:40 ` [v4] " bluez.test.bot
2026-05-15 15:42 ` Luiz Augusto von Dentz
2026-05-20 9:01 ` [PATCH v6 0/2] Add Synaptics BCM4384 Bluetooth support kaihsin Chung
2026-05-20 9:01 ` [PATCH v6 1/2] dt-bindings: net: bluetooth: Add brcm,bcm4384-bt kaihsin Chung
2026-05-20 11:19 ` Krzysztof Kozlowski [this message]
2026-05-20 11:39 ` Add Synaptics BCM4384 Bluetooth support bluez.test.bot
2026-05-20 9:01 ` [PATCH v6 2/2] Bluetooth: btbcm: Add Synaptics 4384 chip support kaihsin Chung
2026-05-27 9:08 ` [PATCH v7 0/2] Add Synaptics BCM4384 Bluetooth support kaihsin Chung
2026-05-27 9:08 ` [PATCH v7 1/2] dt-bindings: net: bluetooth: Add brcm,bcm4384-bt kaihsin Chung
2026-05-27 13:12 ` Krzysztof Kozlowski
2026-05-27 9:08 ` [PATCH v7 2/2] Bluetooth: btbcm: Add Synaptics 4384 chip support kaihsin Chung
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=db9eceed-c136-4d5a-a0a2-5fadf2ab000c@kernel.org \
--to=krzk@kernel.org \
--cc=kaihsin.chung@synaptics.com \
--cc=kaihsin.chung@synaptics.corp-partner.google.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luiz.von.dentz@intel.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