From: Daniel Lezcano <daniel.lezcano@linaro.org>
To: "Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>
Cc: Thomas Gleixner <tglx@linutronix.de>,
Axel Lin <axel.lin@ingics.com>,
linux-kernel@vger.kernel.org, kernel@pengutronix.de,
Ingo Molnar <mingo@kernel.org>
Subject: Re: [PATCH] clocksource: time-efm32: Select CLKSRC_MMIO
Date: Mon, 16 Dec 2013 21:08:21 +0100 [thread overview]
Message-ID: <52AF5DB5.8090302@linaro.org> (raw)
In-Reply-To: <20131210160548.GC18888@pengutronix.de>
On 12/10/2013 05:05 PM, Uwe Kleine-König wrote:
> Hello Daniel,
>
> On Tue, Dec 10, 2013 at 02:29:42PM +0100, Daniel Lezcano wrote:
>> On 12/10/2013 02:24 PM, Uwe Kleine-König wrote:
>>> On Wed, Nov 20, 2013 at 10:15:11AM +0800, Axel Lin wrote:
>>>> The time-efm32 driver uses the clocksource MMIO functions.
>>>> Thus it needs to select CLKSRC_MMIO in Kconfig.
[ ... ]
>> I sent the PR with this patch. If everything is ok, it should be in
>> the next -rc.
> ok. Thanks for your quick reply.
>
> It would be great if your tree were included in linux-next. Don't you
> think this is feasible?
Well, yes it could be a good idea. But if you are suggesting to use
linux-next for the fixes, that should be already taken into account with
the #auto-latest branch of tip.
--
<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-16 20:08 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-20 2:15 [PATCH] clocksource: time-efm32: Select CLKSRC_MMIO Axel Lin
2013-11-20 9:22 ` Uwe Kleine-König
2013-12-10 13:24 ` Uwe Kleine-König
2013-12-10 13:29 ` Daniel Lezcano
2013-12-10 16:05 ` Uwe Kleine-König
2013-12-16 20:08 ` Daniel Lezcano [this message]
2013-12-16 20:54 ` Uwe Kleine-König
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=52AF5DB5.8090302@linaro.org \
--to=daniel.lezcano@linaro.org \
--cc=axel.lin@ingics.com \
--cc=kernel@pengutronix.de \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=tglx@linutronix.de \
--cc=u.kleine-koenig@pengutronix.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 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.