mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Krzysztof Kozlowski <krzk@kernel.org>
To: Vivek Kumar Sahu <vivesahu@qti.qualcomm.com>,
	Marcel Holtmann <marcel@holtmann.org>,
	Luiz Augusto von Dentz <luiz.dentz@gmail.com>,
	Rob Herring <robh@kernel.org>,
	Krzysztof Kozlowski <krzk+dt@kernel.org>,
	Conor Dooley <conor+dt@kernel.org>,
	Bartosz Golaszewski <brgl@bgdev.pl>,
	Balakrishna Godavarthi <quic_bgodavar@quicinc.com>,
	Rocky Liao <quic_rjliao@quicinc.com>
Cc: quic_mohamull@quicinc.com, quic_hbandi@quicinc.com,
	linux-bluetooth@vger.kernel.org, devicetree@vger.kernel.org,
	linux-kernel@vger.kernel.org, linux-arm-msm@vger.kernel.org
Subject: Re: [PATCH 1/2] DT: add bindings for QCC2072 Add DT compatible string "qcom,qcc2072-bt" to yaml file.
Date: Wed, 17 Dec 2025 13:29:45 +0100	[thread overview]
Message-ID: <4bea23cc-68bf-4a78-981d-9798cc1668e8@kernel.org> (raw)
In-Reply-To: <20251217112850.520572-1-vivesahu@qti.qualcomm.com>

On 17/12/2025 12:28, Vivek Kumar Sahu wrote:
> Signed-off-by: Vivek Kumar Sahu <vivesahu@qti.qualcomm.com>
> ---
>  .../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.

Best regards,
Krzysztof

  parent reply	other threads:[~2025-12-17 12:29 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-12-17 11:28 Vivek Kumar Sahu
2025-12-17 11:28 ` [PATCH 2/2] Bluetooth: hci_qca: QCC2072 enablement Vivek Kumar Sahu
2025-12-17 14:29   ` Dmitry Baryshkov
     [not found]     ` <BY5PR02MB69467A78CA2F2929B6618343F186A@BY5PR02MB6946.namprd02.prod.outlook.com>
2026-01-07  7:20       ` Fw: " Vivek Sahu
2026-01-29  5:54         ` Vivek Sahu
2025-12-17 12:16 ` [PATCH 1/2] DT: add bindings for QCC2072 Add DT compatible string "qcom,qcc2072-bt" to yaml file Konrad Dybcio
2025-12-17 12:29 ` Krzysztof Kozlowski [this message]
     [not found]   ` <BY5PR02MB694654EA086696A43CA639DAF189A@BY5PR02MB6946.namprd02.prod.outlook.com>
2026-01-20 10:08     ` Fw: " Vivek Sahu
2025-12-17 14:14 ` Paul Menzel
     [not found]   ` <BY5PR02MB6946637904902544E6767829F189A@BY5PR02MB6946.namprd02.prod.outlook.com>
2026-01-20 10:08     ` Fw: " Vivek Sahu
2026-01-29  5:59       ` Vivek Sahu
2026-01-29 16:18         ` Paul Menzel

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=4bea23cc-68bf-4a78-981d-9798cc1668e8@kernel.org \
    --to=krzk@kernel.org \
    --cc=brgl@bgdev.pl \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=krzk+dt@kernel.org \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=linux-bluetooth@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=luiz.dentz@gmail.com \
    --cc=marcel@holtmann.org \
    --cc=quic_bgodavar@quicinc.com \
    --cc=quic_hbandi@quicinc.com \
    --cc=quic_mohamull@quicinc.com \
    --cc=quic_rjliao@quicinc.com \
    --cc=robh@kernel.org \
    --cc=vivesahu@qti.qualcomm.com \
    /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®