From: Krzysztof Kozlowski <krzk@kernel.org>
To: Cheng Jiang <quic_chejiang@quicinc.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>,
Balakrishna Godavarthi <quic_bgodavar@quicinc.com>,
Rocky Liao <quic_rjliao@quicinc.com>
Cc: linux-bluetooth@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] dt-bindings: bluetooth: Add qca6698 compatible string
Date: Wed, 30 Oct 2024 11:20:49 +0100 [thread overview]
Message-ID: <dd40c783-3c4f-4120-b943-d2594e0e45bb@kernel.org> (raw)
In-Reply-To: <1bc7432e-8032-4af1-8551-75ca53811a18@quicinc.com>
On 30/10/2024 11:18, Cheng Jiang wrote:
> Hi Krzysztof,
>
> We have a new chip(qca6698) to attach on sa8775p-ride board.
>
>
> On 10/30/2024 6:00 PM, Krzysztof Kozlowski wrote:
>> On 30/10/2024 10:47, Cheng Jiang wrote:
>>> Add QCA6698 qcom,qca6698-bt compatible strings.
>>>
>>> Signed-off-by: Cheng Jiang <quic_chejiang@quicinc.com>
>>> ---
>>> Changes in v2:
>>> - Add the compatibility for qcom,qca6698-bt
>>>
>>> ---
>>> .../devicetree/bindings/net/bluetooth/qualcomm-bluetooth.yaml | 2 ++
>>> 1 file changed, 2 insertions(+)
>>
>> Please wait with v2, v3 and so on.
>>
>> Where is any user of this? Nothing in commit msg explains why this patch
>> is needed without users.
>>
Don't top-post. If you have new chip, where is this binding used? I said
there are no users of it and you claim there is some, so where? Point me
to the patch and explain why it is not in this set.
Best regards,
Krzysztof
prev parent reply other threads:[~2024-10-30 10:20 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-30 9:47 [PATCH v2] dt-bindings: bluetooth: Add qca6698 compatible string Cheng Jiang
2024-10-30 10:00 ` Krzysztof Kozlowski
2024-10-30 10:18 ` Cheng Jiang
2024-10-30 10:20 ` Krzysztof Kozlowski [this message]
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=dd40c783-3c4f-4120-b943-d2594e0e45bb@kernel.org \
--to=krzk@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=krzk+dt@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_chejiang@quicinc.com \
--cc=quic_rjliao@quicinc.com \
--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