Skip to contentSkip to conversation

Do not call board_early_init_f() twice

PATCH New Vadim Bendebury 2 participants 2 messages Apr 10, 2013 – Apr 11, 2013

lore
Share & tools
lore
#0 lore raw

PATCH 1/1 Do not call board_early_init_f() twice

Apparently due to a missed rebase conflict resolution board_early_init_f() is included twice in the list of initialization functions.

Leave only the first occurrence.
. built and boot an Exynos 5250 target

---
 common/board_f.c | 3 ---
 1 file changed, 3 deletions(-)
common/board_f.c +0 -3
index 29b49c3..7698891 100644
@@ -788,9 +788,6 @@ static init_fnc_t init_sequence_f[] = {
 	/* TODO: can we rename this to timer_init()? */
 	init_timebase,
 #endif
-#if defined(CONFIG_BOARD_EARLY_INIT_F)
-	board_early_init_f,
-#endif
 #ifdef CONFIG_ARM
 	timer_init,		/* initialize timer */
 #endif
Signature · 1 line
1.8.1.3
#1 lore raw

PATCH 1/1 Do not call board_early_init_f() twice

Quoted 8 lines · Vadim Bendebury

Apparently due to a missed rebase conflict resolution board_early_init_f() is included twice in the list of initialization functions.

Leave only the first occurrence.
. built and boot an Exynos 5250 target

Applied to u-boot/master, thanks!

Signature · 8 lines
Tom
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 836 bytes
Desc: Digital signature
URL: <http://lists.denx.de/pipermail/u-boot/attachments/20130411/0408ce22/attachment.pgp>