From: Alexandre Torgue <alexandre.torgue@st.com>
To: Maxime Coquelin <mcoquelin.stm32@gmail.com>,
Rob Herring <robh+dt@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
Linus Walleij <linus.walleij@linaro.org>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: <devicetree@vger.kernel.org>,
<linux-arm-kernel@lists.infradead.org>,
<linux-kernel@vger.kernel.org>,
Alexandre Torgue <alexandre.torgue@st.com>,
<linux-stm32@st-md-mailman.stormreply.com>,
Manivannan Sadhasivam <manivannan.sadhasivam@linaro.org>,
<linux-gpio@vger.kernel.org>, <linux-usb@vger.kernel.org>
Subject: [PATCH 0/3] dt-bindings: fix issues seen during STM32 DT validation
Date: Mon, 7 Oct 2019 15:44:07 +0200 [thread overview]
Message-ID: <20191007134410.10337-1-alexandre.torgue@st.com> (raw)
This series updates yaml files to clean some issues seen during STM32 device
trees validation.
Alexandre Torgue (3):
dt-bindings: arm: stm32: Add missing STM32 boards
dt-bindings: pinctrl: stm32: Fix 'st,syscfg' description field
dt-bindings: usb: generic-ehci: Add "companion" entry
.../devicetree/bindings/arm/stm32/stm32.yaml | 27 ++++++++++++++++---
.../bindings/pinctrl/st,stm32-pinctrl.yaml | 7 +++--
.../devicetree/bindings/usb/generic-ehci.yaml | 5 ++++
3 files changed, 31 insertions(+), 8 deletions(-)
--
2.17.1
next reply other threads:[~2019-10-07 13:44 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-07 13:44 Alexandre Torgue [this message]
2019-10-07 13:44 ` [PATCH 1/3] dt-bindings: arm: stm32: Add missing STM32 boards Alexandre Torgue
2019-10-15 17:21 ` Rob Herring
2019-10-07 13:44 ` [PATCH 2/3] dt-bindings: pinctrl: stm32: Fix 'st,syscfg' description field Alexandre Torgue
2019-10-15 17:22 ` Rob Herring
2019-10-07 13:44 ` [PATCH 3/3] dt-bindings: usb: generic-ehci: Add "companion" entry Alexandre Torgue
2019-10-15 17:24 ` 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=20191007134410.10337-1-alexandre.torgue@st.com \
--to=alexandre.torgue@st.com \
--cc=devicetree@vger.kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=linus.walleij@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-stm32@st-md-mailman.stormreply.com \
--cc=linux-usb@vger.kernel.org \
--cc=manivannan.sadhasivam@linaro.org \
--cc=mark.rutland@arm.com \
--cc=mcoquelin.stm32@gmail.com \
--cc=robh+dt@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;
as well as URLs for NNTP newsgroup(s).