Re: Fw: [PATCH 1/2] DT: add bindings for QCC2072 Add DT compatible string "qcom,qcc2072-bt" to yaml file.

From: Vivek Sahu

Date: Tue Jan 20 2026 - 05:08:22 EST


________________________________
From: Krzysztof Kozlowski <krzk@xxxxxxxxxx>
Sent: 17 December 2025 17:59
To: Vivek Sahu <vivesahu@xxxxxxxxxxxxxxxx>; Marcel Holtmann <marcel@xxxxxxxxxxxx>; Luiz Augusto von Dentz <luiz.dentz@xxxxxxxxx>; Rob Herring <robh@xxxxxxxxxx>; Krzysztof Kozlowski <krzk+dt@xxxxxxxxxx>; Conor Dooley <conor+dt@xxxxxxxxxx>; Bartosz Golaszewski <brgl@xxxxxxxx>; Balakrishna Godavarthi (QUIC) <quic_bgodavar@xxxxxxxxxxx>; Rocky Liao (QUIC) <quic_rjliao@xxxxxxxxxxx>
Cc: Mohammed Sameer Mulla (QUIC) <quic_mohamull@xxxxxxxxxxx>; Harish Bandi (QUIC) <quic_hbandi@xxxxxxxxxxx>; linux-bluetooth@xxxxxxxxxxxxxxx <linux-bluetooth@xxxxxxxxxxxxxxx>; devicetree@xxxxxxxxxxxxxxx <devicetree@xxxxxxxxxxxxxxx>; linux-kernel@xxxxxxxxxxxxxxx <linux-kernel@xxxxxxxxxxxxxxx>; linux-arm-msm@xxxxxxxxxxxxxxx <linux-arm-msm@xxxxxxxxxxxxxxx>
Subject: Re: [PATCH 1/2] DT: add bindings for QCC2072 Add DT compatible string "qcom,qcc2072-bt" to yaml file.

WARNING: This email originated from outside of Qualcomm. Please be wary of any links or attachments, and do not enable macros.

On 17/12/2025 12:28, Vivek Kumar Sahu wrote:
Signed-off-by: Vivek Kumar Sahu <vivesahu@xxxxxxxxxxxxxxxx>
---
.../devicetree/bindings/net/bluetooth/qualcomm-bluetooth.yaml | 1 +
1 file changed, 1 insertion(+)

diff --git a/Documentation/devicetree/bindings/net/bluetooth/qualcomm-bluetooth.yaml b/Documentation/devicetree/bindings/net/bluetooth/qualcomm-bluetooth.yaml
index 6353a336f382..197248d6f7b8 100644
--- a/Documentation/devicetree/bindings/net/bluetooth/qualcomm-bluetooth.yaml
+++ b/Documentation/devicetree/bindings/net/bluetooth/qualcomm-bluetooth.yaml
@@ -28,6 +28,7 @@ properties:
- qcom,wcn6750-bt
- qcom,wcn6855-bt
- qcom,wcn7850-bt
+ - qcom,qcc2072-bt
This patch fails multiple basic contribution guidelines. Read
instruction how to contribute to upstream and how proper patchset should
look like.
We have identified the problems and are rectifying it. It will be addressed in next patch of this commit.

Best regards,
Krzysztof