From: Alexandre Belloni <alexandre.belloni@bootlin.com>
To: Nicolas Ferre <nicolas.ferre@microchip.com>
Cc: Ludovic Desroches <ludovic.desroches@microchip.com>,
linux-arm-kernel@lists.infradead.org,
Sebastian Reichel <sre@kernel.org>,
linux-kernel@vger.kernel.org, linux-pm@vger.kernel.org
Subject: Re: [PATCH v2 3/3] power: reset: at91-reset: add support for sam9x60 SoC
Date: Fri, 8 Feb 2019 16:24:35 +0100 [thread overview]
Message-ID: <20190208152435.GC23062@piout.net> (raw)
In-Reply-To: <20190206181221.27914-3-nicolas.ferre@microchip.com>
On 06/02/2019 19:12:21+0100, Nicolas Ferre wrote:
> Add support for additional reset causes and the proper compatibility
> string for sam9x60 SoC. The restart function is the same as the samx7.
>
> Signed-off-by: Nicolas Ferre <nicolas.ferre@microchip.com>
> Acked-by: Sebastian Reichel <sebastian.reichel@collabora.com>
Reviewed-by: Alexandre Belloni <alexandre.belloni@bootlin.com>
> ---
> v2: split series and collect tag
>
> Sebastian,
> I add your Acked-by tag here but as I would like that you take the 3 patches on
> your tree now, I let you modify it on your side. I'm expecting Alexandre or
> Ludovic to have a look as well.
>
Sebastian, please take this series through your tree. Thanks!
--
Alexandre Belloni, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2019-02-08 15:24 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-06 18:12 [PATCH v2 1/3] dt-bindings: arm: atmel: add missing samx7 to reset controller Nicolas Ferre
2019-02-06 18:12 ` [PATCH v2 2/3] dt-bindings: arm: atmel: add new sam9x60 reset controller binding Nicolas Ferre
2019-02-08 15:23 ` Alexandre Belloni
2019-02-06 18:12 ` [PATCH v2 3/3] power: reset: at91-reset: add support for sam9x60 SoC Nicolas Ferre
2019-02-08 15:24 ` Alexandre Belloni [this message]
2019-02-19 23:43 ` Sebastian Reichel
2019-02-08 15:23 ` [PATCH v2 1/3] dt-bindings: arm: atmel: add missing samx7 to reset controller Alexandre Belloni
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=20190208152435.GC23062@piout.net \
--to=alexandre.belloni@bootlin.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=ludovic.desroches@microchip.com \
--cc=nicolas.ferre@microchip.com \
--cc=sre@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).