From: Tony Lindgren <tony@atomide.com>
To: Ladislav Michl <ladis@linux-mips.org>
Cc: Keerthy <j-keerthy@ti.com>,
daniel.lezcano@linaro.org, thierry.reding@gmail.com,
aaro.koskinen@iki.fi, Claudiu.Beznea@microchip.com,
narmstrong@baylibre.com, linux-pwm@vger.kernel.org,
s-anna@ti.com, linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
sebastian.reichel@collabora.co.uk, linux-omap@vger.kernel.org,
robh+dt@kernel.org, t-kristo@ti.com, grygorii.strashko@ti.com
Subject: Re: [PATCH v11 04/10] clocksource: timer-ti-dm: Replace architecture
Date: Thu, 22 Feb 2018 10:45:42 -0800 [thread overview]
Message-ID: <20180222184541.GB5184@atomide.com> (raw)
In-Reply-To: <20180222105713.GA30885@lenoch>
* Ladislav Michl <ladis@linux-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@ti.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"
next prev parent reply other threads:[~2018-02-22 18:52 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-15 6:01 [PATCH v11 00/10] omap: dmtimer: Move driver out of plat-omap Keerthy
2018-02-15 6:01 ` [PATCH v11 01/10] clocksource: dmtimer: Remove all the exports Keerthy
2018-02-15 6:01 ` [PATCH v11 02/10] arm: omap: timer: Wrap the inline functions under OMAP2PLUS define Keerthy
2018-02-15 6:01 ` [PATCH v11 03/10] arm: omap: Move dmtimer.h out of plat-omap Keerthy
2018-02-15 6:01 ` [PATCH v11 04/10] clocksource: timer-ti-dm: Replace architecture Keerthy
2018-02-22 10:57 ` Ladislav Michl
2018-02-22 18:45 ` Tony Lindgren [this message]
2018-02-23 4:08 ` Keerthy
2018-02-15 6:01 ` [PATCH v11 05/10] arm: OMAP: Move dmtimer driver out of plat-omap to drivers under clocksource Keerthy
2018-02-15 6:01 ` [PATCH v11 06/10] timer-ti-dm: Add timer ops to the platform data structure Keerthy
2018-02-15 6:01 ` [PATCH v11 07/10] clocksource: timer-ti-dm: Populate the timer ops to the pdata Keerthy
2018-02-15 6:01 ` [PATCH v11 08/10] clocksource: timer-ti-dm: Hook device platform data if not already assigned Keerthy
2018-02-15 6:01 ` [PATCH v11 09/10] pwm: pwm-omap-dmtimer: Adapt driver to utilize dmtimer pdata ops Keerthy
2018-02-15 6:01 ` [PATCH v11 10/10] arm: omap: pdata-quirks: Remove unused timer pdata Keerthy
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=20180222184541.GB5184@atomide.com \
--to=tony@atomide.com \
--cc=Claudiu.Beznea@microchip.com \
--cc=aaro.koskinen@iki.fi \
--cc=daniel.lezcano@linaro.org \
--cc=grygorii.strashko@ti.com \
--cc=j-keerthy@ti.com \
--cc=ladis@linux-mips.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=linux-pwm@vger.kernel.org \
--cc=narmstrong@baylibre.com \
--cc=robh+dt@kernel.org \
--cc=s-anna@ti.com \
--cc=sebastian.reichel@collabora.co.uk \
--cc=t-kristo@ti.com \
--cc=thierry.reding@gmail.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