From: sfr@canb.auug.org.au (Stephen Rothwell)
To: linux-arm-kernel@lists.infradead.org
Subject: linux-next: build failure after merge of the pm tree
Date: Sun, 1 Nov 2015 17:57:18 +1100 [thread overview]
Message-ID: <20151101175718.130f33f2@canb.auug.org.au> (raw)
Hi Rafael,
After merging the pm tree, today's linux-next build (arm
multi_v7_defconfig) failed like this:
arch/arm/mach-mediatek/mediatek.c: In function 'mediatek_timer_init':
arch/arm/mach-mediatek/mediatek.c:43:2: error: implicit declaration of function 'clocksource_of_init' [-Werror=implicit-function-declaration]
clocksource_of_init();
^
Caused by commit
3722ed2380ad ("clocksource: cosmetic: Drop OF 'dependency' from symbols")
interacting with commit
9821e545c5e0 ("ARM: mediatek: enable gpt6 on boot up to make arch timer working")
from the arm-soc tree.
I applied the following merge fix patch for today (someone should tell
Linus when theese trees are merged):
From: Stephen Rothwell <sfr@canb.auug.org.au>
Date: Sun, 1 Nov 2015 17:52:26 +1100
Subject: [PATCH] ARM: mediatek: fixup for clocksource_of_init API change
Signed-off-by: Stephen Rothwell <sfr@canb.auug.org.au>
---
arch/arm/mach-mediatek/mediatek.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/arch/arm/mach-mediatek/mediatek.c b/arch/arm/mach-mediatek/mediatek.c
index 19dc738c1abc..c88a47a3dc37 100644
--- a/arch/arm/mach-mediatek/mediatek.c
+++ b/arch/arm/mach-mediatek/mediatek.c
@@ -40,7 +40,7 @@ static void __init mediatek_timer_init(void)
}
of_clk_init(NULL);
- clocksource_of_init();
+ clocksource_probe();
};
static const char * const mediatek_board_dt_compat[] = {
--
2.6.1
--
Cheers,
Stephen Rothwell sfr at canb.auug.org.au
next reply other threads:[~2015-11-01 6:57 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-01 6:57 Stephen Rothwell [this message]
2015-11-02 0:37 ` linux-next: build failure after merge of the pm tree Rafael J. Wysocki
-- strict thread matches above, loose matches on Subject: below --
2018-05-24 14:16 Mark Brown
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=20151101175718.130f33f2@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--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