mirror of https://lore.kernel.org/lkml/
 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>,
	Mark Rutland <mark.rutland@arm.com>,
	Russell King <linux@armlinux.org.uk>
Cc: <linux-arm-kernel@lists.infradead.org>,
	<devicetree@vger.kernel.org>, <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 0/4] ARM: dts: Add cryptographic support for stm32mp157c
Date: Wed, 2 May 2018 17:50:07 +0200	[thread overview]
Message-ID: <27c3293a-bfbf-6410-68da-6750371e79e6@st.com> (raw)
In-Reply-To: <20180423151947.2526-1-lionel.debieve@st.com>

Hi Lionel,

On 04/23/2018 05:19 PM, Lionel Debieve wrote:
> Patches serie add support or RNG, CRYP and CRC IPs for stm32mp157c SoC
> and add RNG default support for ev1 board.
> 
> Lionel Debieve (4):
>    ARM: dts: stm32: Add RNG support on stm32mp157c
>    ARM: dts: stm32: Enable RNG for stm32mp157c-ed1
>    ARM: dts: stm32: Add CRYP support on stm32mp157c
>    ARM: dts: stm32: Add CRC support on stm32mp157c
> 
>   arch/arm/boot/dts/stm32mp157c-ed1.dts |  4 ++++
>   arch/arm/boot/dts/stm32mp157c.dtsi    | 25 +++++++++++++++++++++++++
>   2 files changed, 29 insertions(+)
> 

Series applied on stm32-next.

Regards
Alex

      parent reply	other threads:[~2018-05-02 15:50 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-04-23 15:19 Lionel Debieve
2018-04-23 15:19 ` [PATCH 1/4] ARM: dts: stm32: Add RNG support on stm32mp157c Lionel Debieve
2018-04-23 15:19 ` [PATCH 2/4] ARM: dts: stm32: Enable RNG for stm32mp157c-ed1 Lionel Debieve
2018-04-23 15:19 ` [PATCH 3/4] ARM: dts: stm32: Add CRYP support on stm32mp157c Lionel Debieve
2018-04-23 15:19 ` [PATCH 4/4] ARM: dts: stm32: Add CRC " Lionel Debieve
2018-05-02 15:50 ` 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=27c3293a-bfbf-6410-68da-6750371e79e6@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@armlinux.org.uk \
    --cc=lionel.debieve@st.com \
    --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

all inboxes | Powered by JetHome®