From: Thierry Reding <thierry.reding@gmail.com>
To: Daniel Lezcano <daniel.lezcano@linaro.org>
Cc: Paul Walmsley <paul@pwsan.com>,
linux-kernel@vger.kernel.org,
Thomas Gleixner <tglx@linutronix.de>,
linux-tegra@vger.kernel.org, Allen Martin <amartin@nvidia.com>,
Stephen Warren <swarren@nvidia.com>,
Thierry Reding <treding@nvidia.com>,
Alexandre Courbot <gnurou@gmail.com>,
pwalmsley@nvidia.com
Subject: Re: [PATCH] clocksource: tegra: wrap arch/arm-specific sections in CONFIG_ARM
Date: Fri, 9 Jan 2015 14:44:19 +0100 [thread overview]
Message-ID: <20150109134417.GA5429@ulmo.nvidia.com> (raw)
In-Reply-To: <54AFD9DF.9090205@linaro.org>
[-- Attachment #1: Type: text/plain, Size: 1006 bytes --]
On Fri, Jan 09, 2015 at 02:38:39PM +0100, Daniel Lezcano wrote:
> On 01/09/2015 02:33 PM, Thierry Reding wrote:
> >On Fri, Jan 09, 2015 at 02:24:24PM +0100, Daniel Lezcano wrote:
> >>On 01/09/2015 01:21 PM, Thierry Reding wrote:
[...]
> >>>How about we do something like the attached patch instead for now. That
> >>>avoids any #ifdef'ery and still we don't attempt (and fail) to build the
> >>>driver on 64-bit ARM.
> >>>
> >>>With that applied we can incrementally make the changes to untangle the
> >>>ARM-specific parts and when the driver can build on 64-bit ARM we simply
> >>>select TEGRA_TIMER via Kconfig.
> >>
> >>Yes, that is exactly what I was thinking about after sending the previous
> >>email. And by this way, you also fixed the Kconfig option selection logic.
> >
> >Great. Will you give your Acked-by so that I can take that patch through
> >the Tegra tree to resolve the build dependency?
>
> Acked-by: Daniel Lezcano <daniel.lezcano@linaro.org>
Thanks,
Thierry
[-- Attachment #2: Type: application/pgp-signature, Size: 819 bytes --]
next prev parent reply other threads:[~2015-01-09 13:44 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-09 22:07 [PATCH] clocksource: tegra: wrap arch/arm-specific sections in CONFIG_ARM Paul Walmsley
[not found] ` <alpine.DEB.2.02.1412092201200.31750-rwI8Ez+7Ko+d5PgPZx9QOdBPR1lH4CV8@public.gmane.org>
2014-12-10 11:14 ` Thierry Reding
2014-12-10 11:14 ` Thierry Reding
[not found] ` <20141210111425.GD15287-AwZRO8vwLAwmlAP/+Wk3EA@public.gmane.org>
2014-12-12 2:13 ` Paul Walmsley
2014-12-12 2:13 ` Paul Walmsley
2014-12-12 2:13 ` Paul Walmsley
2015-01-07 14:29 ` Thierry Reding
2015-01-07 14:29 ` Thierry Reding
2015-01-08 16:58 ` Daniel Lezcano
2015-01-08 16:58 ` Daniel Lezcano
2015-01-09 2:09 ` Paul Walmsley
2015-01-09 8:31 ` Daniel Lezcano
[not found] ` <54AF91CC.2090007-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org>
2015-01-09 12:21 ` Thierry Reding
2015-01-09 12:21 ` Thierry Reding
2015-01-09 13:24 ` Daniel Lezcano
2015-01-09 13:24 ` Daniel Lezcano
[not found] ` <54AFD688.5000304-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org>
2015-01-09 13:33 ` Thierry Reding
2015-01-09 13:33 ` Thierry Reding
2015-01-09 13:38 ` Daniel Lezcano
2015-01-09 13:44 ` Thierry Reding [this message]
2015-01-08 14:21 ` Daniel Lezcano
[not found] ` <54AE9286.1090800-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org>
2015-01-08 15:48 ` Thierry Reding
2015-01-08 15:48 ` Thierry Reding
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=20150109134417.GA5429@ulmo.nvidia.com \
--to=thierry.reding@gmail.com \
--cc=amartin@nvidia.com \
--cc=daniel.lezcano@linaro.org \
--cc=gnurou@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=paul@pwsan.com \
--cc=pwalmsley@nvidia.com \
--cc=swarren@nvidia.com \
--cc=tglx@linutronix.de \
--cc=treding@nvidia.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.