From: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
To: Magnus Damm <magnus.damm@gmail.com>
Cc: linux-kernel@vger.kernel.org, khilman@linaro.org, arnd@arndb.de,
linux-sh@vger.kernel.org, daniel.lezcano@linaro.org,
horms@verge.net.au, olof@lixom.net, tglx@linutronix.de
Subject: Re: [PATCH v2 00/03] clocksource: Consolidate SH and ARM mach-shmobile Kconfig bits
Date: Wed, 06 Nov 2013 23:20:25 +0100 [thread overview]
Message-ID: <6099086.0MXoMDIj69@avalon> (raw)
In-Reply-To: <20131106110508.6806.48070.sendpatchset@w520>
Hi Magnus,
Thanks for the patches.
On Wednesday 06 November 2013 20:05:08 Magnus Damm wrote:
> clocksource: Consolidate SH and ARM mach-shmobile Kconfig bits (v2)
>
> [PATCH v2 01/03] clocksource: Add Kconfig entries for CMT, MTU2, TMU and STI
> [PATCH v2 02/03] ARM: shmobile: Remove CMT, TMU and STI Kconfig entries
> [PATCH v2 03/03] sh: Remove Kconfig entries for TMU, CMT and MTU2
>
> This is V2 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
> or when COMPILE_TEST is selected.
>
> Since last time this has been broken out into 3 separate patches,
> where [PATCH v2 01/03] needs to go first, and the other patches
> can be merged any time after without any build or configuration
> issues.
>
> Thanks to Olof and Simon for feedback! If I interpreted your
> ideas wrong please let me know and I will update.
>
> Signed-off-by: Magnus Damm <damm@opensource.se>
I like this approach.
Acked-by: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
> ---
>
> Written against renesas.git tag renesas-devel-v3.12-rc7-20131101
>
> arch/arm/mach-shmobile/Kconfig | 21 ---------------------
> arch/sh/Kconfig | 21 ---------------------
> drivers/clocksource/Kconfig | 30 ++++++++++++++++++++++++++++++
> 3 files changed, 30 insertions(+), 42 deletions(-)
--
Regards,
Laurent Pinchart
prev parent reply other threads:[~2013-11-06 22:19 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-06 11:05 [PATCH v2 00/03] clocksource: Consolidate SH and ARM mach-shmobile Kconfig bits Magnus Damm
2013-11-06 11:05 ` [PATCH v2 01/03] clocksource: Add Kconfig entries for CMT, MTU2, TMU and STI Magnus Damm
2013-11-07 11:27 ` Daniel Lezcano
2013-11-08 8:23 ` Magnus Damm
2013-11-08 18:34 ` John Stultz
2013-11-12 12:26 ` Magnus Damm
2013-11-12 20:47 ` John Stultz
2013-11-13 21:14 ` Daniel Lezcano
2013-11-13 21:25 ` John Stultz
2013-11-28 5:42 ` Magnus Damm
2013-12-02 23:08 ` John Stultz
2013-12-04 13:30 ` Magnus Damm
2013-11-13 21:38 ` John Stultz
2013-11-14 12:40 ` Arnd Bergmann
2013-11-20 8:33 ` Daniel Lezcano
2013-11-20 18:31 ` John Stultz
2013-11-20 19:34 ` Arnd Bergmann
2013-11-20 19:53 ` John Stultz
2013-11-06 11:05 ` [PATCH v2 02/03] ARM: shmobile: Remove CMT, TMU and STI Kconfig entries Magnus Damm
2013-11-06 11:05 ` [PATCH v2 03/03] sh: Remove Kconfig entries for TMU, CMT and MTU2 Magnus Damm
2013-11-06 22:20 ` Laurent Pinchart [this message]
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=6099086.0MXoMDIj69@avalon \
--to=laurent.pinchart@ideasonboard.com \
--cc=arnd@arndb.de \
--cc=daniel.lezcano@linaro.org \
--cc=horms@verge.net.au \
--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