Hi Geert,
I'll verify that on the new tree, and start bisecting. Sigh.
Good luck!
7c5fd5619dc89fb52d2c2cf144fc6e4365427b86 is first bad commit
commit 7c5fd5619dc89fb52d2c2cf144fc6e4365427b86
Author: Tim Abbott <tabbott@xxxxxxxxxxx>
Date: Sun Sep 27 13:57:55 2009 -0400
m68k: Cleanup linker scripts using new linker script macros.
Signed-off-by: Tim Abbott <tabbott@xxxxxxxxxxx>
Tested-by: Andreas Schwab <schwab@xxxxxxxxxxxxxx>
Cc: Roman Zippel <zippel@xxxxxxxxxxxxxx>
Cc: Sam Ravnborg <sam@xxxxxxxxxxxx>
Signed-off-by: Geert Uytterhoeven <geert@xxxxxxxxxxxxxx>
:040000 040000 5bdbf7ce5dd4ea2f23669c6a6ec11192865b5bfa
d3b7397533b0af6261747ccef3cff9cd40f6baf9 M arch
Backing out that commit on the top of the tree results in a bootable
2.6.33-rc2 for me
The order of symbols in the system map is different (as you would expect)
but I don't see what implicit assumption woule be violated.
Michael
--
To unsubscribe from this list: send the line "unsubscribe linux-m68k" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
