From: Daniel Lezcano <daniel.lezcano@linaro.org>
To: Guenter Roeck <linux@roeck-us.net>,
Oleksij Rempel <linux@rempel-privat.de>,
linux-kernel@vger.kernel.org, tglx@linutronix.de
Subject: Re: [PATCH] clocksource: whitelist asm9260_timer driver for ARM
Date: Wed, 18 Feb 2015 09:47:53 +0100 [thread overview]
Message-ID: <54E451B9.7010809@linaro.org> (raw)
In-Reply-To: <54E43C96.6060008@roeck-us.net>
On 02/18/2015 08:17 AM, Guenter Roeck wrote:
> On 02/10/2015 07:57 AM, Oleksij Rempel wrote:
>> For now it is easier to allow only tested platforms, instead of
>> fighting with different platform specific issues.
>>
>> This patch is fixing compile error on ARCH=SPARC and SPARC64:
>>
>> Building sparc64:allmodconfig ... failed
>> --------------
>> Error log:
>> drivers/built-in.o: In function `asm9260_timer_init':
>> asm9260_timer.c:(.init.text+0x60d4): undefined reference to
>> `of_io_request_and_map'
>>
>> Tested-by: Guenter Roeck <linux@roeck-us.net>
>> Reported-by: Guenter Roeck <linux@roeck-us.net>
>> Signed-off-by: Oleksij Rempel <linux@rempel-privat.de>
>
> The problem solved by this patch has affected linux-next
> for almost a month, the problem is now in mainline, yet
> I have not seen feedback from anyone about it.
>
> Did the patch get lost, or is there some problem with it ?
No problem with it. Just I have been out of the office for a couple of
weeks. I will take care of this patch and some other I received in the
meantime.
Thanks
-- Daniel
>> ---
>> drivers/clocksource/Kconfig | 2 +-
>> 1 file changed, 1 insertion(+), 1 deletion(-)
>>
>> diff --git a/drivers/clocksource/Kconfig b/drivers/clocksource/Kconfig
>> index bfaaae4..39d5c11 100644
>> --- a/drivers/clocksource/Kconfig
>> +++ b/drivers/clocksource/Kconfig
>> @@ -231,7 +231,7 @@ config CLKSRC_MIPS_GIC
>>
>> config ASM9260_TIMER
>> bool "Alphascale ASM9260 timer driver"
>> - depends on GENERIC_CLOCKEVENTS
>> + depends on GENERIC_CLOCKEVENTS && ARM
>> select CLKSRC_MMIO
>> select CLKSRC_OF
>> default y if MACH_ASM9260
>>
>
--
<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:[~2015-02-18 8:47 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-09 10:18 linux-next: Tree for Feb 9 Stephen Rothwell
2015-02-09 17:20 ` linux-next: Tree for Feb 9 (build failures) Guenter Roeck
2015-02-10 7:07 ` Oleksij Rempel
2015-02-10 12:14 ` Guenter Roeck
2015-02-10 15:57 ` [PATCH] clocksource: whitelist asm9260_timer driver for ARM Oleksij Rempel
2015-02-18 7:17 ` Guenter Roeck
2015-02-18 8:47 ` Daniel Lezcano [this message]
2015-02-23 17:48 ` Daniel Lezcano
2015-02-23 17:57 ` Guenter Roeck
2015-02-23 18:57 ` Daniel Lezcano
2015-02-23 19:00 ` [PATCH] clockevents: asm9260: Fix compilation error with sparc/sparc64 allyesconfig Daniel Lezcano
2015-02-23 19:10 ` Guenter Roeck
2015-02-23 20:27 ` Oleksij Rempel
2015-02-23 20:34 ` Guenter Roeck
2015-02-23 20:46 ` Oleksij Rempel
2015-02-23 20:49 ` Guenter Roeck
2015-02-23 21:21 ` Daniel Lezcano
2015-02-24 5:16 ` Oleksij Rempel
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=54E451B9.7010809@linaro.org \
--to=daniel.lezcano@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@rempel-privat.de \
--cc=linux@roeck-us.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