From: Alexandre Torgue <alexandre.torgue@st.com>
To: Maxime Ripard <mripard@kernel.org>,
Mauro Carvalho Chehab <mchehab@kernel.org>,
Rob Herring <robh+dt@kernel.org>,
Mark Rutland <mark.rutland@arm.com>, Chen-Yu Tsai <wens@csie.org>,
Alexandru Ardelean <alexaundru.ardelean@analog.com>,
Liam Girdwood <lgirdwood@gmail.com>,
Mark Brown <broonie@kernel.org>
Cc: <devicetree@vger.kernel.org>,
<linux-arm-kernel@lists.infradead.org>,
<linux-kernel@vger.kernel.org>,
Alexandre Torgue <alexandre.torgue@st.com>,
<linux-media@vger.kernel.org>, <netdev@vger.kernel.org>
Subject: [PATCH 0/3] Fixes for dt-bindings verification
Date: Mon, 7 Oct 2019 12:25:49 +0200 [thread overview]
Message-ID: <20191007102552.19808-1-alexandre.torgue@st.com> (raw)
Using "make dt_binding_check" on top v5.4-rc1 some errors are
reported in several schemas. Those 3 patches allow to execute
"make dt_binding_check" without issues. Most probably those patches
have alread been sent.
regards
Alexandre
Alexandre Torgue (3):
dt-bindings: media: Fix id path for sun4i-a10-csi
dt-bindings: net: adi: Fix yaml verification issue
dt-bindings: regulator: Fix yaml verification for fixed-regulator
schema
.../bindings/media/allwinner,sun4i-a10-csi.yaml | 2 +-
Documentation/devicetree/bindings/net/adi,adin.yaml | 6 ++++++
.../devicetree/bindings/regulator/fixed-regulator.yaml | 10 +++++++---
3 files changed, 14 insertions(+), 4 deletions(-)
--
2.17.1
next reply other threads:[~2019-10-07 10:26 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-07 10:25 Alexandre Torgue [this message]
2019-10-07 10:25 ` [PATCH 1/3] dt-bindings: media: Fix id path for sun4i-a10-csi Alexandre Torgue
2019-10-07 11:00 ` Maxime Ripard
2019-10-07 14:08 ` Alexandre Torgue
2019-10-07 10:25 ` [PATCH 2/3] dt-bindings: net: adi: Fix yaml verification issue Alexandre Torgue
2019-10-07 13:56 ` Rob Herring
2019-10-07 14:07 ` Alexandre Torgue
2019-10-07 10:25 ` [PATCH 3/3] dt-bindings: regulator: Fix yaml verification for fixed-regulator schema Alexandre Torgue
2019-10-07 13:08 ` Rob Herring
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=20191007102552.19808-1-alexandre.torgue@st.com \
--to=alexandre.torgue@st.com \
--cc=alexaundru.ardelean@analog.com \
--cc=broonie@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=lgirdwood@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=mchehab@kernel.org \
--cc=mripard@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=robh+dt@kernel.org \
--cc=wens@csie.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).