From: "Dwivedi, Avaneesh Kumar (avani)" <akdwived@codeaurora.org>
To: Bryan O'Donoghue <bryan.odonoghue@linaro.org>,
linux-arm-msm@vger.kernel.org, linux-usb@vger.kernel.org,
devicetree@vger.kernel.org
Cc: linux-kernel@vger.kernel.org, ckadabi@codeaurora.org,
tsoni@codeaurora.org, bryanh@codeaurora.org,
psodagud@codeaurora.org, rnayak@codeaurora.org,
satyap@codeaurora.org, pheragu@codeaurora.org
Subject: Re: [PATCH v4 1/2] dt-bindings: Documentation for qcom,eud
Date: Sun, 16 Feb 2020 18:44:56 +0530 [thread overview]
Message-ID: <cbd9adaf-7333-ede3-d407-0ccbe91a2f4c@codeaurora.org> (raw)
In-Reply-To: <f06e6af6-5045-ce75-fcc6-e07890b3a29c@linaro.org>
On 2/4/2020 8:47 AM, Bryan O'Donoghue wrote:
> On 31/01/2020 04:43, Avaneesh Kumar Dwivedi wrote:
>> Documentation for Embedded USB Debugger (EUD) device tree bindings.
>>
>> Signed-off-by: Satya Durga Srinivasu Prabhala <satyap@codeaurora.org>
>> Signed-off-by: Prakruthi Deepak Heragu <pheragu@codeaurora.org>
>> Signed-off-by: Avaneesh Kumar Dwivedi <akdwived@codeaurora.org>
>> ---
>> .../devicetree/bindings/soc/qcom/qcom,msm-eud.txt | 43
>> ++++++++++++++++++++++
>> 1 file changed, 43 insertions(+)
>> create mode 100644
>> Documentation/devicetree/bindings/soc/qcom/qcom,msm-eud.txt
>
> Forgot to mention, this file should be described in YAML.
Ok
>
> ./Documentation/devicetree/writing-schema.rst
> ./Documentation/devicetree/bindings/example-schema.yaml
>
> ---
> bod
--
Qualcomm India Private Limited, on behalf of Qualcomm Innovation Center, Inc. is a member of the Code Aurora Forum,
a Linux Foundation Collaborative Project.
next prev parent reply other threads:[~2020-02-16 13:15 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-31 4:43 [PATCH v4 0/2] Add Embedded USB Debugger (EUD) driver Avaneesh Kumar Dwivedi
2020-01-31 4:43 ` [PATCH v4 1/2] dt-bindings: Documentation for qcom,eud Avaneesh Kumar Dwivedi
2020-02-04 2:51 ` Bryan O'Donoghue
2020-02-16 13:11 ` Dwivedi, Avaneesh Kumar (avani)
2020-02-04 3:17 ` Bryan O'Donoghue
2020-02-16 13:14 ` Dwivedi, Avaneesh Kumar (avani) [this message]
2020-01-31 4:43 ` [PATCH v4 2/2] Embedded USB Debugger (EUD) driver Avaneesh Kumar Dwivedi
2020-02-03 19:35 ` Bjorn Andersson
2020-02-04 3:10 ` Bryan O'Donoghue
2020-02-16 16:07 ` Dwivedi, Avaneesh Kumar (avani)
2020-02-17 19:44 ` Bryan O'Donoghue
2020-02-18 13:23 ` Dwivedi, Avaneesh Kumar (avani)
2020-02-18 14:48 ` Bryan O'Donoghue
2020-04-04 14:12 ` Dwivedi, Avaneesh Kumar (avani)
2020-02-16 14:14 ` Dwivedi, Avaneesh Kumar (avani)
2020-02-18 3:35 ` Bjorn Andersson
2020-02-18 13:00 ` Dwivedi, Avaneesh Kumar (avani)
2020-02-07 10:04 ` Greg KH
2020-02-16 16:22 ` Dwivedi, Avaneesh Kumar (avani)
2020-02-16 16:35 ` Greg KH
2020-02-17 7:21 ` Dwivedi, Avaneesh Kumar (avani)
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=cbd9adaf-7333-ede3-d407-0ccbe91a2f4c@codeaurora.org \
--to=akdwived@codeaurora.org \
--cc=bryan.odonoghue@linaro.org \
--cc=bryanh@codeaurora.org \
--cc=ckadabi@codeaurora.org \
--cc=devicetree@vger.kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=pheragu@codeaurora.org \
--cc=psodagud@codeaurora.org \
--cc=rnayak@codeaurora.org \
--cc=satyap@codeaurora.org \
--cc=tsoni@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).