From: Philipp Zabel <p.zabel@pengutronix.de>
To: Joel Stanley <joel@jms.id.au>, Rob Herring <robh+dt@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
Andrew Jeffery <andrew@aj.id.au>
Cc: Lee Jones <lee.jones@linaro.org>,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-aspeed@lists.ozlabs.org
Subject: Re: [PATCH 0/3] reset: simple: enable for ASPEED SoCs
Date: Mon, 19 Feb 2018 12:46:10 +0100 [thread overview]
Message-ID: <1519040770.3408.5.camel@pengutronix.de> (raw)
In-Reply-To: <20180219065438.19933-1-joel@jms.id.au>
Hi Joel,
On Mon, 2018-02-19 at 17:24 +1030, Joel Stanley wrote:
> Hello Philip,
>
> Here is a series that enables the simple reset driver for the ASPEED
> SoCs. You may recall I posted a patch back in May 2017 with a
> similar idea[1]. I was happy to see that you merged a driver that solves
> the problem, and suits our purpose for the ASPEED. Thanks!
Yes, sometimes it takes a few drivers to see what the common patterns
are. When it came to unify them, starting from one of the preexisting
drivers seemed like the straightforward thing to do.
regards
Philipp
prev parent reply other threads:[~2018-02-19 11:46 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-19 6:54 [PATCH 0/3] reset: simple: enable for ASPEED SoCs Joel Stanley
2018-02-19 6:54 ` [PATCH 1/3] dt-bindings: aspeed-lpc: Add reset controller Joel Stanley
2018-02-19 11:46 ` Philipp Zabel
2018-02-19 12:00 ` Joel Stanley
2018-02-19 20:41 ` Rob Herring
2018-02-19 6:54 ` [PATCH 2/3] reset: simple: Enable for ASPEED systems Joel Stanley
2018-02-19 6:54 ` [PATCH 3/3] reset: simple: Allow user selection of driver Joel Stanley
2018-02-19 11:46 ` Philipp Zabel
2018-02-19 12:07 ` Joel Stanley
2018-02-19 11:46 ` Philipp Zabel [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=1519040770.3408.5.camel@pengutronix.de \
--to=p.zabel@pengutronix.de \
--cc=andrew@aj.id.au \
--cc=devicetree@vger.kernel.org \
--cc=joel@jms.id.au \
--cc=lee.jones@linaro.org \
--cc=linux-aspeed@lists.ozlabs.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.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).