From: Sebastian Reichel <sre@kernel.org>
To: Linus Walleij <linus.walleij@linaro.org>
Cc: Dmitry Eremin-Solenikov <dbaryshkov@gmail.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
David Woodhouse <dwmw2@infradead.org>,
Rob Herring <robh@kernel.org>, Arnd Bergmann <arnd@arndb.de>
Subject: Re: [PATCH 1/2] power/reset: versatile: support the actual versatile
Date: Mon, 15 Feb 2016 05:59:19 +0100 [thread overview]
Message-ID: <20160215045919.GB28626@earth> (raw)
In-Reply-To: <CACRpkdb4dP6Wr9FVo5H-jCTq-iD-OA6t-Gvs1O=hNZ11DAX8mw@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1041 bytes --]
Hi,
On Thu, Feb 11, 2016 at 03:40:51PM +0100, Linus Walleij wrote:
> Hi knock knock,
>
> On Mon, Jan 25, 2016 at 9:29 AM, Linus Walleij <linus.walleij@linaro.org> wrote:
>
> > While this driver is named after the Versatile family of
> > boards (ARM reference designs) the machine actually called
> > Versatile was not supported. This patch makes the driver
> > handle also that machine. We augment the register names for
> > the reset to *VERSATILE* as well since it is the same
> > register offsets for Versatile and RealView.
> >
> > Cc: Rob Herring <robh@kernel.org>
> > Signed-off-by: Linus Walleij <linus.walleij@linaro.org>
> > ---
> > Hi Power folks, since this is orthogonal to the corresponding
> > device tree changes it's best of this is just merged into the
> > power tree and I'll merge the required device tree and board
> > file changes into the ARM SoC tree.
>
> Would the power/reset maintainers please apply this patch or
> provide some feedback?
Sorry for the delay, queued.
-- Sebastian
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
prev parent reply other threads:[~2016-02-15 4:59 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-25 8:29 [PATCH 1/2] power/reset: versatile: support the actual versatile Linus Walleij
2016-02-11 14:40 ` Linus Walleij
2016-02-15 4:59 ` Sebastian Reichel [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=20160215045919.GB28626@earth \
--to=sre@kernel.org \
--cc=arnd@arndb.de \
--cc=dbaryshkov@gmail.com \
--cc=dwmw2@infradead.org \
--cc=linus.walleij@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=robh@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