From: santosh shilimkar <santosh.shilimkar@oracle.com>
To: Kevin Hilman <khilman@kernel.org>,
Rajendra Nayak <rnayak@codeaurora.org>
Cc: rjw@rjwysocki.net, ssantosh@kernel.org, tony@atomide.com,
nsekhar@ti.com, magnus.damm@gmail.com,
linux-arm-msm@vger.kernel.org,
inux-arm-kernel@lists.infradead.org, linux-pm@vger.kernel.org,
linux-omap@vger.kernel.org, linux-sh@vger.kernel.org
Subject: Re: [RFC 0/5] PM / clock_ops: provide default runtime ops and cleanup users
Date: Mon, 20 Apr 2015 16:25:25 -0700 [thread overview]
Message-ID: <55358AE5.1070900@oracle.com> (raw)
In-Reply-To: <7hfv7ue68c.fsf@deeprootsystems.com>
On 4/20/2015 4:21 PM, Kevin Hilman wrote:
> Rajendra Nayak <rnayak@codeaurora.org> writes:
>
>> Most users of PM clocks do the exact same thing in runtime callbacks.
>
> Probably because they were all copied from mach-davinci. ;)
>
Yep. ;-)
>> Provide default callbacks and cleanup the existing users (keystone/davinci/omap1/sh)
>
> Very nice cleanup, Thanks!
>
Indeed !!
I can't test it out but from the series, I don't expect anything
to break. So looks good to me as well.
> For the series:
>
> Reviewed-by: Kevin Hilman <khilman@linaro.org>
>
Acked-by: Santosh Shilimkar <ssantosh@kernel.org>
next prev parent reply other threads:[~2015-04-20 23:25 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-14 13:34 [RFC 0/5] PM / clock_ops: provide default runtime ops and cleanup users Rajendra Nayak
2015-04-14 13:34 ` [RFC 1/5] PM / clock_ops: Provide default runtime ops to users Rajendra Nayak
2015-04-14 13:34 ` [RFC 2/5] arm: keystone: remove boilerplate code and use USE_PM_CLK_RUNTIME_OPS Rajendra Nayak
2015-04-14 13:34 ` [RFC 3/5] arm: omap1: " Rajendra Nayak
2015-04-14 13:34 ` [RFC 4/5] arm: davinci: " Rajendra Nayak
2015-04-14 13:34 ` [RFC 5/5] drivers: sh: " Rajendra Nayak
2015-04-20 23:21 ` [RFC 0/5] PM / clock_ops: provide default runtime ops and cleanup users Kevin Hilman
2015-04-20 23:25 ` santosh shilimkar [this message]
2015-04-21 8:01 ` Geert Uytterhoeven
2015-04-21 8:56 ` Rajendra Nayak
2015-04-21 9:04 ` Geert Uytterhoeven
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=55358AE5.1070900@oracle.com \
--to=santosh.shilimkar@oracle.com \
--cc=inux-arm-kernel@lists.infradead.org \
--cc=khilman@kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=linux-sh@vger.kernel.org \
--cc=magnus.damm@gmail.com \
--cc=nsekhar@ti.com \
--cc=rjw@rjwysocki.net \
--cc=rnayak@codeaurora.org \
--cc=ssantosh@kernel.org \
--cc=tony@atomide.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