linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: daniel.lezcano@linaro.org (Daniel Lezcano)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] clocksource: ftm: select CLKSRC_MMIO
Date: Thu, 14 Jan 2016 10:25:40 +0100	[thread overview]
Message-ID: <56976994.2060205@linaro.org> (raw)
In-Reply-To: <11970328.RVc8t0Mk1C@wuerfel>

On 01/14/2016 12:02 AM, Arnd Bergmann wrote:
> The ftm clocksource driver does not build if CLKSRC_MMIO is disabled:
>
> drivers/built-in.o: In function `ftm_timer_init':
> (init.text+0xd324): undefined reference to `clocksource_mmio_init'
> (init.text+0xd484): undefined reference to `clocksource_mmio_readl_up'
>
> This adds the same 'select' statement that the other similar drivers
> use. Prior to allowing this driver to be enabled with COMPILE_TEST,
> it was apparently unused. I'm not entirely sure who is using this
> hardware, but it certainly can't hurt to ensure it builds cleanly.

Hi Arnd,

Thanks for the fix. It is already in Thomas's tree [1].

It has been merged in tip/timers/urgent. You will have to wait a bit 
this branch to be merged with tip/timers/core.

   -- Daniel

[1] 
https://git.kernel.org/cgit/linux/kernel/git/tip/tip.git/commit/?h=timers/urgent&id=03724ac3d48f8f0e3caf1d30fa134f8fd96c94e2



-- 
  <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

  reply	other threads:[~2016-01-14  9:25 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-01-13 23:02 [PATCH] clocksource: ftm: select CLKSRC_MMIO Arnd Bergmann
2016-01-14  9:25 ` Daniel Lezcano [this message]
2016-01-14 12:23   ` Arnd Bergmann

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=56976994.2060205@linaro.org \
    --to=daniel.lezcano@linaro.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    /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).