PM / clock_ops: provide default runtime ops and cleanup users
Get series with b4
b4 am [email protected]Versions newest first
- v1 Latest0 of 5 patches 0 repliesNew
Patches in v1 No applies recorded yet
None of the 5 patches the cover letter announces are in this archive.
Reviews trailers per patch
| Patch | Simon Horman |
|---|---|
| Series | A-b |
Trailers given in replies are filled; those carried in the patches from earlier versions are outlined with dashes.
Cover letter [PATCH 0/5] PM / clock_ops: provide default runtime ops and cleanup users
Quoted 20 lines · Rafael J. Wysocki
Quoted 11 lines · Rajendra Nayak
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 useUSE_PM_CLK_RUNTIME_OPS
arm: omap1: remove boilerplate code and useUSE_PM_CLK_RUNTIME_OPS
arm: davinci: remove boilerplate code and useUSE_PM_CLK_RUNTIME_OPS
drivers: sh: remove boilerplate code and useUSE_PM_CLK_RUNTIME_OPSQuoted 7 lines
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(-)
Quoted 4 lines
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.
Regards,
Santosh