From: mturquette@linaro.org (Mike Turquette)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 1/1] clk/exynos4: Fix compilation warning
Date: Wed, 28 May 2014 00:57:07 -0700 [thread overview]
Message-ID: <20140528075707.10062.7113@quantum> (raw)
In-Reply-To: <1401077788-31427-1-git-send-email-sachin.kamat@linaro.org>
Quoting Sachin Kamat (2014-05-25 21:16:28)
> Fixes the following warning:
> WARNING: drivers/built-in.o(.text.unlikely+0x2c50): Section mismatch in reference from the function exynos4_clk_sleep_init() to the (unknown reference) .init.data:(unknown)
> The function exynos4_clk_sleep_init() references
> the (unknown reference) __initdata (unknown).
> This is often because exynos4_clk_sleep_init lacks a __initdata
> annotation or the annotation of (unknown) is wrong.
>
> Signed-off-by: Sachin Kamat <sachin.kamat@linaro.org>
> Reported-by: kbuild test robot <fengguang.wu@intel.com>
Applied to clk-next.
Thanks!
Mike
> ---
> drivers/clk/samsung/clk-exynos4.c | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/clk/samsung/clk-exynos4.c b/drivers/clk/samsung/clk-exynos4.c
> index c4df294bb7fb..4f150c9dd38c 100644
> --- a/drivers/clk/samsung/clk-exynos4.c
> +++ b/drivers/clk/samsung/clk-exynos4.c
> @@ -324,7 +324,7 @@ static struct syscore_ops exynos4_clk_syscore_ops = {
> .resume = exynos4_clk_resume,
> };
>
> -static void exynos4_clk_sleep_init(void)
> +static void __init exynos4_clk_sleep_init(void)
> {
> exynos4_save_common = samsung_clk_alloc_reg_dump(exynos4_clk_regs,
> ARRAY_SIZE(exynos4_clk_regs));
> @@ -359,7 +359,7 @@ err_warn:
> __func__);
> }
> #else
> -static void exynos4_clk_sleep_init(void) {}
> +static void __init exynos4_clk_sleep_init(void) {}
> #endif
>
> /* list of all parent clock list */
> --
> 1.7.9.5
>
prev parent reply other threads:[~2014-05-28 7:57 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-26 4:16 [PATCH 1/1] clk/exynos4: Fix compilation warning Sachin Kamat
2014-05-28 7:57 ` Mike Turquette [this message]
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=20140528075707.10062.7113@quantum \
--to=mturquette@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).