On Thu, Feb 27, 2014 at 07:44:58AM -0500, Jason Cooper wrote:
Shawn,
Not sure if you follow the autobuild mailinglist. If not, then fyi: this is new as of last night.
Thanks, Jason.
I receive the error report from 0-DAY kbuild test robot a few hours ago, and I have queued a fix on my for-next branch, so I expect this will go away with the next linux-next build.
Shawn
We (mvebu) just created multi_v5_defconfig, so we'll look into that from our end.
thx,
Jason.
On Wed, Feb 26, 2014 at 11:06:25PM -0800, Olof's autobuilder wrote:
Here are the build results from automated periodic testing.
The tree being built was next, found at:
http://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git (master branch)
Topmost commit:
8dd7fbe Add linux-next specific files for 20140227
Build logs (stderr only) can be found at the following link (experimental):
http://arm-soc.lixom.net/buildlogs/next/next-20140227/
Runtime: 44m 40s
Passed: 123 Failed: 2
Warnings: 78
Section mismatches: 38
Failed defconfigs: imx_v4_v5_defconfig multi_v5_defconfig
Errors:
imx_v4_v5_defconfig: :(.text+0x2c40): undefined reference to `v7_invalidate_l1'
multi_v5_defconfig: arch/arm/mach-imx/suspend-imx6.S:358: undefined reference to `v7_invalidate_l1'