[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20180222184541.GB5184@atomide.com>
Date: Thu, 22 Feb 2018 10:45:42 -0800
From: Tony Lindgren <tony@...mide.com>
To: Ladislav Michl <ladis@...ux-mips.org>
Cc: Keerthy <j-keerthy@...com>, daniel.lezcano@...aro.org,
thierry.reding@...il.com, aaro.koskinen@....fi,
Claudiu.Beznea@...rochip.com, narmstrong@...libre.com,
linux-pwm@...r.kernel.org, s-anna@...com,
linux-kernel@...r.kernel.org, linux-arm-kernel@...ts.infradead.org,
sebastian.reichel@...labora.co.uk, linux-omap@...r.kernel.org,
robh+dt@...nel.org, t-kristo@...com, grygorii.strashko@...com
Subject: Re: [PATCH v11 04/10] clocksource: timer-ti-dm: Replace architecture
* Ladislav Michl <ladis@...ux-mips.org> [180222 10:58]:
> On Thu, Feb 15, 2018 at 11:31:45AM +0530, Keerthy wrote:
> > Replace architecture specific guard with clocksource guard.
> >
> > Signed-off-by: Keerthy <j-keerthy@...com>
> > Replace architecture specific defines with clocksource
>
> This looks like a bit unussual commit log. Also, what about merging
> it with previous patch?
I'll just remove that line locally to avoid yet another set
of patches being posted :)
> Btw, I tested whole serie again on the top of today's -next and it is
> still working fine. What is preventing these patches from being merged?
Well I noticed we need a fix for omap1 that I just posted.
And patch 4/10 needs the following select for omap16xx that
I'll fold in.
I'll push it all to omap-for-v4.17/timer and will merge into
my for-next after some more testing. It seems any further
patching can be done after move to drivers.
Regards,
Tony
8< -----------------
--- a/arch/arm/mach-omap1/Kconfig
+++ b/arch/arm/mach-omap1/Kconfig
@@ -30,6 +30,7 @@ config ARCH_OMAP16XX
bool "OMAP16xx Based System"
select ARCH_OMAP_OTG
select CPU_ARM926T
+ select OMAP_DM_TIMER
config OMAP_MUX
bool "OMAP multiplexing support"
Powered by blists - more mailing lists