From: Rob Herring <robh@kernel.org>
To: Benjamin Gaignard <benjamin.gaignard@st.com>
Cc: srinivas.kandagatla@linaro.org, robh+dt@kernel.org,
mark.rutland@arm.com, mcoquelin.stm32@gmail.com,
alexandre.torgue@st.com, fabrice.gasnier@st.com,
devicetree@vger.kernel.org,
linux-stm32@st-md-mailman.stormreply.com,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org,
Benjamin Gaignard <benjamin.gaignard@st.com>
Subject: Re: [PATCH 1/3] dt-bindings: nvmem: Convert STM32 ROMEM to json-schema
Date: Fri, 20 Dec 2019 15:54:48 -0700 [thread overview]
Message-ID: <20191220225448.GA5275@bogus> (raw)
In-Reply-To: <20191219144117.21527-2-benjamin.gaignard@st.com>
On Thu, 19 Dec 2019 15:41:15 +0100, Benjamin Gaignard wrote:
> Convert the STM32 ROMEM binding to DT schema format using json-schema
>
> Signed-off-by: Benjamin Gaignard <benjamin.gaignard@st.com>
> ---
> .../devicetree/bindings/nvmem/st,stm32-romem.txt | 31 ---------------
> .../devicetree/bindings/nvmem/st,stm32-romem.yaml | 46 ++++++++++++++++++++++
> 2 files changed, 46 insertions(+), 31 deletions(-)
> delete mode 100644 Documentation/devicetree/bindings/nvmem/st,stm32-romem.txt
> create mode 100644 Documentation/devicetree/bindings/nvmem/st,stm32-romem.yaml
>
Applied, thanks.
Rob
next prev parent reply other threads:[~2019-12-20 22:54 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-19 14:41 [PATCH 0/3] Convert STM32 ROMEM to json-schema Benjamin Gaignard
2019-12-19 14:41 ` [PATCH 1/3] dt-bindings: nvmem: " Benjamin Gaignard
2019-12-20 22:54 ` Rob Herring [this message]
2019-12-19 14:41 ` [PATCH 2/3] ARM: dts: stm32: change nvmem node name on stm32f429 Benjamin Gaignard
2019-12-19 14:41 ` [PATCH 3/3] ARM: dts: stm32: change nvmem node name on stm32mp1 Benjamin Gaignard
2020-01-09 9:01 ` [PATCH 0/3] Convert STM32 ROMEM to json-schema Alexandre Torgue
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=20191220225448.GA5275@bogus \
--to=robh@kernel.org \
--cc=alexandre.torgue@st.com \
--cc=benjamin.gaignard@st.com \
--cc=devicetree@vger.kernel.org \
--cc=fabrice.gasnier@st.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-stm32@st-md-mailman.stormreply.com \
--cc=mark.rutland@arm.com \
--cc=mcoquelin.stm32@gmail.com \
--cc=robh+dt@kernel.org \
--cc=srinivas.kandagatla@linaro.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).