From: Sagar Kadam <sagar.kadam@sifive.com>
To: linux-kernel@vger.kernel.org
Cc: devicetree@vger.kernel.org, aou@eecs.berkeley.edu,
yash.shah@sifive.com, robh+dt@kernel.org, palmer@dabbelt.com,
Sagar Kadam <sagar.kadam@sifive.com>,
paul.walmsley@sifive.com, linux-riscv@lists.infradead.org
Subject: [RESEND PATCH v2 0/1] convert l2 cache dt bindings to YAML format
Date: Fri, 28 Aug 2020 22:25:42 +0530 [thread overview]
Message-ID: <1598633743-1023-1-git-send-email-sagar.kadam@sifive.com> (raw)
Resending it, since subject lines of earlier v2 patches missed the file
sequence like PATCH 0/1 and 1/1.
This patch is created and tested on top of mainline linux
commit d012a7190fc1 ("Linux 5.9-rc2")
Reference log of "make dt_binding_check" is available here[1].
I was able to reproduce the error after excluding the DT_SCHEMA_FILES
option. Just in case required the failure log is here[2].
[1] https://paste.ubuntu.com/p/R5b52vCkKJ/
[2] https://paste.ubuntu.com/p/gwYY3hd9Rx/
Change History:
====================
V2:
-Fixed bot failure mentioned by Rob Herring
-Updated dt-schema and kernel as suggested
V1:
Base version
Sagar Kadam (1):
dt-bindings: riscv: sifive-l2-cache: convert bindings to json-schema
.../devicetree/bindings/riscv/sifive-l2-cache.txt | 51 ------------
.../devicetree/bindings/riscv/sifive-l2-cache.yaml | 92 ++++++++++++++++++++++
2 files changed, 92 insertions(+), 51 deletions(-)
delete mode 100644 Documentation/devicetree/bindings/riscv/sifive-l2-cache.txt
create mode 100644 Documentation/devicetree/bindings/riscv/sifive-l2-cache.yaml
--
2.7.4
_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv
next reply other threads:[~2020-08-28 17:00 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-28 16:55 Sagar Kadam [this message]
2020-08-28 16:55 ` [RESEND PATCH v2 1/1] dt-bindings: riscv: sifive-l2-cache: convert bindings to json-schema Sagar Kadam
2020-09-14 18:00 ` Rob Herring
2020-09-15 15:17 ` Sagar Kadam
2020-09-22 19:27 ` Rob Herring
2020-09-23 17:30 ` Sagar Kadam
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=1598633743-1023-1-git-send-email-sagar.kadam@sifive.com \
--to=sagar.kadam@sifive.com \
--cc=aou@eecs.berkeley.edu \
--cc=devicetree@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=palmer@dabbelt.com \
--cc=paul.walmsley@sifive.com \
--cc=robh+dt@kernel.org \
--cc=yash.shah@sifive.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;
as well as URLs for NNTP newsgroup(s).