devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Alexandre Torgue <alexandre.torgue@st.com>
To: Lionel Debieve <lionel.debieve@st.com>,
	Maxime Coquelin <mcoquelin.stm32@gmail.com>,
	Rob Herring <robh+dt@kernel.org>
Cc: <linux-arm-kernel@lists.infradead.org>,
	<devicetree@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
	<linux-stm32@st-md-mailman.stormreply.com>,
	Nicolas Toromanoff <nicolas.toromanoff@st.com>
Subject: Re: [PATCH 0/3] ARM: dts: stm32: enable crypto controllers
Date: Mon, 9 Nov 2020 12:08:48 +0100	[thread overview]
Message-ID: <28f5e745-bdac-7cc1-62a9-745e8d41a142@st.com> (raw)
In-Reply-To: <20201105102331.12984-1-lionel.debieve@st.com>

Hi Lionel

On 11/5/20 11:23 AM, Lionel Debieve wrote:
> Enable the crypto controllers in the STM32MP157C-EV1 and STM32MP157A-DK1
> STM32MP157C-DK2 boards.
> 
> Lionel Debieve (2):
>    ARM: dts: stm32: enable HASH by default on stm32mp15
>    ARM: dts: stm32: enable CRYP by default on stm32mp15
> 
> Nicolas Toromanoff (1):
>    ARM: dts: stm32: enable CRC1 by default on stm32mp15
> 
>   arch/arm/boot/dts/stm32mp157c-dk2.dts  |  4 ++++
>   arch/arm/boot/dts/stm32mp157c-ed1.dts  | 12 ++++++++++++
>   arch/arm/boot/dts/stm32mp15xx-dkx.dtsi |  8 ++++++++
>   3 files changed, 24 insertions(+)
> 

Series applied on stm32-next.

Regards
Alex

      parent reply	other threads:[~2020-11-09 11:09 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-11-05 10:23 [PATCH 0/3] ARM: dts: stm32: enable crypto controllers Lionel Debieve
2020-11-05 10:23 ` [PATCH 1/3] ARM: dts: stm32: enable HASH by default on stm32mp15 Lionel Debieve
2020-11-05 10:23 ` [PATCH 2/3] ARM: dts: stm32: enable CRC1 " Lionel Debieve
2020-11-05 10:23 ` [PATCH 3/3] ARM: dts: stm32: enable CRYP " Lionel Debieve
2020-11-09 11:08 ` 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=28f5e745-bdac-7cc1-62a9-745e8d41a142@st.com \
    --to=alexandre.torgue@st.com \
    --cc=devicetree@vger.kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-stm32@st-md-mailman.stormreply.com \
    --cc=lionel.debieve@st.com \
    --cc=mcoquelin.stm32@gmail.com \
    --cc=nicolas.toromanoff@st.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).