From: Alexandre Torgue <alexandre.torgue@st.com>
To: Benjamin Gaignard <benjamin.gaignard@st.com>,
<srinivas.kandagatla@linaro.org>, <robh+dt@kernel.org>,
<mark.rutland@arm.com>, <mcoquelin.stm32@gmail.com>,
<fabrice.gasnier@st.com>
Cc: <devicetree@vger.kernel.org>,
<linux-stm32@st-md-mailman.stormreply.com>,
<linux-arm-kernel@lists.infradead.org>,
<linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 0/3] Convert STM32 ROMEM to json-schema
Date: Thu, 9 Jan 2020 10:01:02 +0100 [thread overview]
Message-ID: <c3326bf5-f3f8-489b-5245-3b9fd47324bb@st.com> (raw)
In-Reply-To: <20191219144117.21527-1-benjamin.gaignard@st.com>
Hi Benjamin,
On 12/19/19 3:41 PM, Benjamin Gaignard wrote:
> Convert STM32 ROMEM to json-schema and fix the issues detected on stm32 dtsi
> files.
> Note that stm32mp1 patch should be applied on top of the stm32-next tree.
>
> Benjamin Gaignard (3):
> dt-bindings: nvmem: Convert STM32 ROMEM to json-schema
> ARM: dts: stm32: change nvmem node name on stm32f429
> ARM: dts: stm32: change nvmem node name on stm32mp1
>
> .../devicetree/bindings/nvmem/st,stm32-romem.txt | 31 ---------------
> .../devicetree/bindings/nvmem/st,stm32-romem.yaml | 46 ++++++++++++++++++++++
> arch/arm/boot/dts/stm32f429.dtsi | 2 +-
> arch/arm/boot/dts/stm32mp151.dtsi | 2 +-
> 4 files changed, 48 insertions(+), 33 deletions(-)
> delete mode 100644 Documentation/devicetree/bindings/nvmem/st,stm32-romem.txt
> create mode 100644 Documentation/devicetree/bindings/nvmem/st,stm32-romem.yaml
>
DT patches applied on stm32-next.
Thanks
Alex
prev parent reply other threads:[~2020-01-09 9:01 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
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 ` Alexandre Torgue [this message]
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=c3326bf5-f3f8-489b-5245-3b9fd47324bb@st.com \
--to=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).