From: Philipp Zabel <p.zabel@pengutronix.de>
To: Paul Gortmaker <paul.gortmaker@windriver.com>
Cc: linux-kernel@vger.kernel.org, Alban Bedel <albeu@free.fr>,
Carlo Caione <carlo@caione.org>,
Damien Horsley <Damien.Horsley@imgtec.com>,
Kevin Hilman <khilman@baylibre.com>,
linux-amlogic@lists.infradead.org,
linux-oxnas@lists.tuxfamily.org,
Neil Armstrong <narmstrong@baylibre.com>
Subject: Re: [PATCH 0/4] reset: de-modularize the remaining reset drivers
Date: Wed, 08 Feb 2017 11:43:39 +0100 [thread overview]
Message-ID: <1486550619.2309.36.camel@pengutronix.de> (raw)
In-Reply-To: <20170208001847.9887-1-paul.gortmaker@windriver.com>
Hi Paul,
On Tue, 2017-02-07 at 19:18 -0500, Paul Gortmaker wrote:
> Recently, a new reset driver was added that used module stuff in a
> driver that was clearly non-modular[1]. With that in mind, it is
> probably wise to get the remaining patches I have locally for the
> existing reset drivers out the door, so we don't get any more
> future instances of a new driver copying the old error once again.
Applied, much appreciated.
I'll wait a bit for the remaining authors' Acked-by:s and then push them
out.
regards
Philipp
prev parent reply other threads:[~2017-02-08 11:21 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-08 0:18 [PATCH 0/4] reset: de-modularize the remaining reset drivers Paul Gortmaker
2017-02-08 0:18 ` [PATCH 1/4] reset: ath79: make it explicitly non-modular Paul Gortmaker
2017-02-09 9:03 ` Alban
2017-02-08 0:18 ` [PATCH 2/4] reset: pistachio: " Paul Gortmaker
2017-02-08 0:18 ` [PATCH 3/4] reset: meson: " Paul Gortmaker
2017-02-08 8:43 ` Neil Armstrong
2017-02-08 0:18 ` [PATCH 4/4] reset: oxnas: " Paul Gortmaker
2017-02-08 8:44 ` Neil Armstrong
2017-02-08 10:43 ` 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=1486550619.2309.36.camel@pengutronix.de \
--to=p.zabel@pengutronix.de \
--cc=Damien.Horsley@imgtec.com \
--cc=albeu@free.fr \
--cc=carlo@caione.org \
--cc=khilman@baylibre.com \
--cc=linux-amlogic@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-oxnas@lists.tuxfamily.org \
--cc=narmstrong@baylibre.com \
--cc=paul.gortmaker@windriver.com \
/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