From: Daniel Lezcano <daniel.lezcano@linaro.org>
To: Ingo Molnar <mingo@kernel.org>
Cc: tglx@linutronix.de, matthias.bgg@gmail.com,
robert.jarzmik@free.fr, linux@roeck-us.net,
linux@rempel-privat.de, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 3/3] clocksource: pxa: Fix section mismatch
Date: Wed, 25 Feb 2015 11:45:38 +0100 [thread overview]
Message-ID: <54EDA7D2.2040203@linaro.org> (raw)
In-Reply-To: <20150225103555.GC554@gmail.com>
On 02/25/2015 11:35 AM, Ingo Molnar wrote:
>
> * Daniel Lezcano <daniel.lezcano@linaro.org> wrote:
>
>> From: Robert Jarzmik <robert.jarzmik@free.fr>
>>
>> As pxa_timer_common_init() is only called in init context, mark it as
>> such, and quiesce the compiler warnings :
>> WARNING: vmlinux.o(.text.unlikely+0x45d4): Section mismatch in reference
>> from the function pxa_timer_common_init() to the function
>> .init.text:sched_clock_register()
>>
>> WARNING: vmlinux.o(.text.unlikely+0x4610): Section mismatch in reference
>> from the function pxa_timer_common_init() to the function
>> .init.text:clocksource_mmio_init()
>>
>> Signed-off-by: Robert Jarzmik <robert.jarzmik@free.fr>
>> Signed-off-by: Daniel Lezcano <daniel.lezcano@linaro.org>
>> ---
>> drivers/clocksource/pxa_timer.c | 2 +-
>> 1 file changed, 1 insertion(+), 1 deletion(-)
>>
>> diff --git a/drivers/clocksource/pxa_timer.c b/drivers/clocksource/pxa_timer.c
>> index 941f3f3..d9438af 100644
>> --- a/drivers/clocksource/pxa_timer.c
>> +++ b/drivers/clocksource/pxa_timer.c
>> @@ -163,7 +163,7 @@ static struct irqaction pxa_ost0_irq = {
>> .dev_id = &ckevt_pxa_osmr0,
>> };
>>
>> -static void pxa_timer_common_init(int irq, unsigned long clock_tick_rate)
>> +static void __init pxa_timer_common_init(int irq, unsigned long clock_tick_rate)
>> {
>> timer_writel(0, OIER);
>> timer_writel(OSSR_M0 | OSSR_M1 | OSSR_M2 | OSSR_M3, OSSR);
>
> So this is then used indirectly by:
>
> CLOCKSOURCE_OF_DECLARE(pxa_timer, "marvell,pxa-timer", pxa_timer_dt_init);
>
> which should probably be marked __initdata?
Sorry, I miss the point. What should be marked __initdata ?
--
<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-25 10:45 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <54EDA19F.7050903@linaro.org>
2015-02-25 10:31 ` [PATCH 1/3] clockevents: asm9260: Fix compilation error with sparc/sparc64 allyesconfig Daniel Lezcano
2015-02-25 10:31 ` [PATCH 2/3] clocksource: mtk: Fix race conditions in probe code Daniel Lezcano
2015-02-25 10:31 ` [PATCH 3/3] clocksource: pxa: Fix section mismatch Daniel Lezcano
2015-02-25 10:35 ` Ingo Molnar
2015-02-25 10:45 ` Daniel Lezcano [this message]
2015-02-25 10:48 ` Ingo Molnar
2015-02-25 10:56 ` Daniel Lezcano
2015-02-25 10:59 ` Ingo Molnar
2015-02-25 11:18 [GIT PULL][resend] clockevents fixes for 4.0-rc1 Daniel Lezcano
2015-02-25 11:19 ` [PATCH 1/3] clockevents: asm9260: Fix compilation error with sparc/sparc64 allyesconfig Daniel Lezcano
2015-02-25 11:19 ` [PATCH 3/3] clocksource: pxa: Fix section mismatch Daniel Lezcano
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=54EDA7D2.2040203@linaro.org \
--to=daniel.lezcano@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@rempel-privat.de \
--cc=linux@roeck-us.net \
--cc=matthias.bgg@gmail.com \
--cc=mingo@kernel.org \
--cc=robert.jarzmik@free.fr \
--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 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.