From: Daniel Lezcano <daniel.lezcano@linaro.org>
To: Magnus Damm <magnus.damm@gmail.com>, linux-kernel@vger.kernel.org
Cc: khilman@linaro.org, arnd@arndb.de, linux-sh@vger.kernel.org,
horms@verge.net.au, john.stultz@linaro.org, olof@lixom.net,
tglx@linutronix.de
Subject: Re: [PATCH v5 00/03] clocksource: Consolidate SH and ARM mach-shmobile Kconfig bits
Date: Wed, 18 Dec 2013 15:38:35 +0000 [thread overview]
Message-ID: <52B1C17B.6060500@linaro.org> (raw)
In-Reply-To: <20131217101212.17491.56898.sendpatchset@w520>
On 12/17/2013 11:12 AM, Magnus Damm wrote:
> clocksource: Consolidate SH and ARM mach-shmobile Kconfig bits (v5)
>
> [PATCH v5 01/03] clocksource: Add Kconfig entries for CMT, MTU2, TMU and STI
> [PATCH v5 02/03] ARM: shmobile: Remove CMT, TMU and STI Kconfig entries
> [PATCH v5 03/03] sh: Remove Kconfig entries for TMU, CMT and MTU2
>
> This is V5 of the SH and ARM mach-shmobile clocksource Kconfig
> consolidation series.
>
> By sharing Kconfig entires in drivers/clocksource/Kconfig we
> can get rid of duplicated bits that do not belong under arch/.
>
> With this series applied it is possible to build the timer
> drivers for CMT, MTU2, TMU and STI in case of SH or ARM. The timer
> drivers are automatically selected by default. It is also possible
> to select and/or deselect freely when COMPILE_TEST has been selected.
>
> Many thanks to Olof, John, Daniel and Arnd for feedback!
>
> Changes since V4:
> - Use SYS_SUPPORTS_SH/EM to avoid name space pollution, thanks Olof!
> - Remove old SH entries for SYS_SUPPORTS_xxx, use above SH prefix instead
>
> Changes since V3:
> - Updated patch 1/3 with more detailed help texts
> - Updated patch 2/3 to fit latest renesas-devel tag, see below
> - Included acks from John Stultz for patch 2/3 and 3/3
>
> Signed-off-by: Magnus Damm <damm@opensource.se>
> ---
>
> Written against renesas.git tag renesas-devel-v3.13-rc3-20131214v2
Do you want me to take the patchset ? If so, could you respin it against
timers/core ?
Thanks
-- Daniel
>
> arch/arm/mach-shmobile/Kconfig | 35 ++++++++----------
> arch/sh/Kconfig | 76 ++++++++++++----------------------------
> drivers/clocksource/Kconfig | 44 +++++++++++++++++++++++
> 3 files changed, 84 insertions(+), 71 deletions(-)
>
--
<http://www.linaro.org/> Linaro.org │ Open source software for ARM SoCs
Follow Linaro: <http://www.facebook.com/pages/Linaro> Facebook |
<http://twitter.com/#!/linaroorg> Twitter |
<http://www.linaro.org/linaro-blog/> Blog
next prev parent reply other threads:[~2013-12-18 15:38 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-17 10:12 [PATCH v5 00/03] clocksource: Consolidate SH and ARM mach-shmobile Kconfig bits Magnus Damm
2013-12-17 10:12 ` [PATCH v5 01/03] clocksource: Add Kconfig entries for CMT, MTU2, TMU and STI Magnus Damm
2013-12-17 10:12 ` [PATCH v5 02/03] ARM: shmobile: Remove CMT, TMU and STI Kconfig entries Magnus Damm
2013-12-17 10:13 ` [PATCH v5 03/03] sh: Remove Kconfig entries for TMU, CMT and MTU2 Magnus Damm
2013-12-18 15:38 ` Daniel Lezcano [this message]
2013-12-18 22:24 ` [PATCH v5 00/03] clocksource: Consolidate SH and ARM mach-shmobile Kconfig bits Magnus Damm
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=52B1C17B.6060500@linaro.org \
--to=daniel.lezcano@linaro.org \
--cc=arnd@arndb.de \
--cc=horms@verge.net.au \
--cc=john.stultz@linaro.org \
--cc=khilman@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sh@vger.kernel.org \
--cc=magnus.damm@gmail.com \
--cc=olof@lixom.net \
--cc=tglx@linutronix.de \
/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).