From: Rob Herring <robh@kernel.org>
To: Zijun Hu <zijuhu@codeaurora.org>
Cc: davem@davemloft.net, rjliao@codeaurora.org, kuba@kernel.org,
bgodavar@codeaurora.org, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-bluetooth@vger.kernel.org,
devicetree@vger.kernel.org, Zijun Hu <quic_zijuhu@quicinc.com>
Subject: Re: [PATCH v1 2/3] dt-bindings: net: bluetooth: Add device tree bindings for QTI bluetooth MAPLE
Date: Fri, 12 Nov 2021 11:02:07 -0600 [thread overview]
Message-ID: <YY6eD/r3ddU7PUxJ@robh.at.kernel.org> (raw)
In-Reply-To: <1635837069-1293-1-git-send-email-zijuhu@codeaurora.org>
On Tue, Nov 02, 2021 at 03:11:09PM +0800, Zijun Hu wrote:
> From: Zijun Hu <quic_zijuhu@quicinc.com>
Subject space is valuable, don't say things twice:
dt-bindings: net: bluetooth: Add Qualcomm MAPLE
Is MAPLE an SoC? Everything else used part numbers, why not here?
>
> Add device tree bindings for QTI bluetooth MAPLE.
>
> Signed-off-by: Zijun Hu <quic_zijuhu@quicinc.com>
> ---
> Documentation/devicetree/bindings/net/qualcomm-bluetooth.yaml | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/Documentation/devicetree/bindings/net/qualcomm-bluetooth.yaml b/Documentation/devicetree/bindings/net/qualcomm-bluetooth.yaml
> index f93c6e7a1b59..9f0508c4dd16 100644
> --- a/Documentation/devicetree/bindings/net/qualcomm-bluetooth.yaml
> +++ b/Documentation/devicetree/bindings/net/qualcomm-bluetooth.yaml
> @@ -23,6 +23,7 @@ properties:
> - qcom,wcn3998-bt
> - qcom,qca6390-bt
> - qcom,wcn6750-bt
> + - qcom,maple-bt
>
> enable-gpios:
> maxItems: 1
> --
> The Qualcomm Innovation Center, Inc. is a member of the Code Aurora Forum, a Linux Foundation Collaborative Project
>
>
next prev parent reply other threads:[~2021-11-12 17:02 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-02 7:11 [PATCH v1 2/3] dt-bindings: net: bluetooth: Add device tree bindings for QTI bluetooth MAPLE Zijun Hu
2021-11-12 17:02 ` Rob Herring [this message]
2021-11-14 12:34 ` zijuhu
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=YY6eD/r3ddU7PUxJ@robh.at.kernel.org \
--to=robh@kernel.org \
--cc=bgodavar@codeaurora.org \
--cc=davem@davemloft.net \
--cc=devicetree@vger.kernel.org \
--cc=kuba@kernel.org \
--cc=linux-bluetooth@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=quic_zijuhu@quicinc.com \
--cc=rjliao@codeaurora.org \
--cc=zijuhu@codeaurora.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.