From: "Rafael J. Wysocki" <rjw@rjwysocki.net>
To: Kevin Hilman <khilman@baylibre.com>
Cc: "Heiko Stübner" <heiko@sntech.de>,
"David Wu" <david.wu@rock-chips.com>,
nm@ti.com, huangtao@rock-chips.com, cf@rock-chips.com,
zyw@rock-chips.com, xjq@rock-chips.com,
linux-arm-kernel@lists.infradead.org,
linux-rockchip@lists.infradead.org, linux-pm@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] PM / AVS: rockchip-io: add io selectors and supplies for rk3399
Date: Wed, 23 Mar 2016 22:24:44 +0100 [thread overview]
Message-ID: <3859377.YHUlbhqqCy@vostro.rjw.lan> (raw)
In-Reply-To: <7h8u19q6dw.fsf@baylibre.com>
On Wednesday, March 23, 2016 01:35:55 PM Kevin Hilman wrote:
> Heiko Stübner <heiko@sntech.de> writes:
>
> > Hi David,
> >
> > Am Mittwoch, 16. März 2016, 02:45:26 schrieb David Wu:
> >> This adds the necessary data for handling io voltage domains on the rk3399.
> >> As interesting tidbit, the rk3399 contains two separate iodomain areas.
> >> One in the regular General Register Files (GRF) and one in PMUGRF in the
> >> pmu power domain.
> >>
> >> Signed-off-by: David Wu <david.wu@rock-chips.com>
> >
> > looks good, so
> > Reviewed-by: Heiko Stuebner <heiko@sntech.de>
>
> Acked-by: Kevin Hilman <khilman@baylibre.com>
>
> Rafael, can you queue this directly? I don't currently have any other
> AVS patches in the queue.
OK, applied.
That said it's the last minute for this to get into 4.6, so I'd appreciate
getting ACKs earlier during merge windows.
Thanks,
Rafael
next prev parent reply other threads:[~2016-03-23 21:24 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-15 18:45 [PATCH] PM / AVS: rockchip-io: add io selectors and supplies for rk3399 David Wu
2016-03-16 11:11 ` Heiko Stübner
2016-03-23 20:35 ` Kevin Hilman
2016-03-23 21:24 ` Rafael J. Wysocki [this message]
2016-03-23 21:44 ` Kevin Hilman
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=3859377.YHUlbhqqCy@vostro.rjw.lan \
--to=rjw@rjwysocki.net \
--cc=cf@rock-chips.com \
--cc=david.wu@rock-chips.com \
--cc=heiko@sntech.de \
--cc=huangtao@rock-chips.com \
--cc=khilman@baylibre.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=nm@ti.com \
--cc=xjq@rock-chips.com \
--cc=zyw@rock-chips.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