linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: horms@verge.net.au (Simon Horman)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 0/5] PM / clock_ops: provide default runtime ops and cleanup users
Date: Tue, 28 Apr 2015 09:46:19 +0900	[thread overview]
Message-ID: <20150428004618.GA1807@verge.net.au> (raw)
In-Reply-To: <553A6289.4040001@oracle.com> <CAMuHMdWMjULD8jQDA-U6tumnCd=Q7jhZ2koha4CKU-K50tJXmw@mail.gmail.com>

On Fri, Apr 24, 2015 at 04:51:03PM +0200, Geert Uytterhoeven wrote:
> On Fri, Apr 24, 2015 at 4:41 PM, Rafael J. Wysocki <rjw@rjwysocki.net> wrote:
> > On Thursday, April 23, 2015 02:03:08 PM Rajendra Nayak wrote:
> >> Most users of PM clocks do the exact same thing in runtime callbacks.
> >> Provide default callbacks and cleanup the existing users (keystone/davinci
> >> /omap1/sh)
> >>
> >> Rajendra Nayak (5):
> >>   PM / clock_ops: Provide default runtime ops to users
> >>   arm: keystone: remove boilerplate code and use USE_PM_CLK_RUNTIME_OPS
> >>   arm: omap1: remove boilerplate code and use USE_PM_CLK_RUNTIME_OPS
> >>   arm: davinci: remove boilerplate code and use USE_PM_CLK_RUNTIME_OPS
> >>   drivers: sh: remove boilerplate code and use USE_PM_CLK_RUNTIME_OPS
> >>
> >>  arch/arm/mach-davinci/pm_domain.c  | 32 +-------------------------
> >>  arch/arm/mach-keystone/pm_domain.c | 33 +-------------------------
> >>  arch/arm/mach-omap1/pm_bus.c       | 37 ++----------------------------
> >>  drivers/base/power/clock_ops.c     | 38 ++++++++++++++++++++++++++++++
> >>  drivers/sh/pm_runtime.c            | 47 ++------------------------------------
> >>  include/linux/pm_clock.h           | 10 ++++++++
> >>  6 files changed, 54 insertions(+), 143 deletions(-)
> >
> > It is not particularly clear to me who is supposed to apply this series, but
> > I can do that if people don't have problems with that.
> 
> All later patches depend on the first patch.
> 
> For shmobile, Simon has queued up changes for drivers/sh/pm_runtime.c,
> but I think they don't conflict with this series.

Yes, that is the case. I have some patches (from Geert) queued up for v4.1.
I have confirmed that they do not conflict with the shmobile (last) patch
if this series.

<details>
The patches are in the sh-drivers-for-v4.1 branch of my renesas tree; I
rebased them yesterday; they should hit next today if there is a next
today; I plan to send a pull request to Linus in the not to distant future;
and I envisage they should end up in v4.1-rc2 or rc3.  </details>

On Fri, Apr 24, 2015 at 08:34:33AM -0700, santosh shilimkar wrote:
> On 4/24/2015 7:41 AM, Rafael J. Wysocki wrote:
> >On Thursday, April 23, 2015 02:03:08 PM Rajendra Nayak wrote:

[snip]

> >It is not particularly clear to me who is supposed to apply this series, but
> >I can do that if people don't have problems with that.
> >
> >
> I am fine by that given dependency with first patch.
> Another way is, you pick up the first patch and give us an
> immutable branch.
> 
> Either way is fine by me.

Likewise.

Here is an ack for the shmobile (last) patch if you decide to take it
through your tree.

Acked-by: Simon Horman <horms+renesas@verge.net.au>

  reply	other threads:[~2015-04-28  0:46 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-23  8:33 [PATCH 0/5] PM / clock_ops: provide default runtime ops and cleanup users Rajendra Nayak
2015-04-23  8:33 ` [PATCH 1/5] PM / clock_ops: Provide default runtime ops to users Rajendra Nayak
2015-04-23  8:33 ` [PATCH 2/5] arm: keystone: remove boilerplate code and use USE_PM_CLK_RUNTIME_OPS Rajendra Nayak
2015-04-23  8:33 ` [PATCH 3/5] arm: omap1: " Rajendra Nayak
2015-04-24 15:31   ` Tony Lindgren
2015-04-23  8:33 ` [PATCH 4/5] arm: davinci: " Rajendra Nayak
2015-04-23  8:33 ` [PATCH 5/5] drivers: sh: " Rajendra Nayak
2015-04-24  7:57 ` [PATCH 0/5] PM / clock_ops: provide default runtime ops and cleanup users Ulf Hansson
2015-04-24 14:41 ` Rafael J. Wysocki
2015-04-24 14:51   ` Geert Uytterhoeven
2015-04-28  0:46     ` Simon Horman [this message]
2015-05-01  1:09       ` Simon Horman
2015-04-24 15:34   ` santosh shilimkar

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=20150428004618.GA1807@verge.net.au \
    --to=horms@verge.net.au \
    --cc=linux-arm-kernel@lists.infradead.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).