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:
1b0a7e3 Add linux-next specific files for 20140307
Build logs (stderr only) can be found at the following link (experimental):
http://arm-soc.lixom.net/buildlogs/next/next-20140307/
Runtime: 45m 24s
Passed: 116 Failed: 9
Warnings: 78
Section mismatches: 38
-------------------------------------------------------------------------------
Failed defconfigs: dove_defconfig ebsa110_defconfig efm32_defconfig kirkwood_defconfig multi_v5_defconfig mv78xx0_defconfig mvebu_v5_defconfig mvebu_v7_defconfig orion5x_defconfig
-------------------------------------------------------------------------------
Errors:
dove_defconfig: kernel/irq/Kconfig:41:error: recursive dependency detected! drivers/i2c/busses/i2c-mv64xxx.c:924: undefined reference to `reset_control_assert' drivers/i2c/busses/i2c-mv64xxx.c:904: undefined reference to `reset_control_assert'
ebsa110_defconfig: kernel/irq/Kconfig:41:error: recursive dependency detected! drivers/mcb/mcb-parse.c:105:2: error: implicit declaration of function 'memcpy_fromio' [-Werror=implicit-function-declaration]
efm32_defconfig: kernel/irq/Kconfig:41:error: recursive dependency detected! arch/arm/kernel/sleep.S:133: Error: selected processor does not support requested special purpose register -- `mrs r1,cpsr' arch/arm/kernel/sleep.S:133: Error: selected processor does not support requested special purpose register -- `msr spsr_cxsf,r1' arch/arm/kernel/sleep.S:133: Error: selected processor does not support requested special purpose register -- `msr cpsr_c,r1'
kirkwood_defconfig: kernel/irq/Kconfig:41:error: recursive dependency detected! drivers/i2c/busses/i2c-mv64xxx.c:924: undefined reference to `reset_control_assert' drivers/i2c/busses/i2c-mv64xxx.c:904: undefined reference to `reset_control_assert' drivers/i2c/busses/i2c-mv64xxx.c:771: undefined reference to `devm_reset_control_get' drivers/i2c/busses/i2c-mv64xxx.c:778: undefined reference to `reset_control_deassert'
multi_v5_defconfig: kernel/irq/Kconfig:41:error: recursive dependency detected! drivers/i2c/busses/i2c-mv64xxx.c:924: undefined reference to `reset_control_assert' drivers/i2c/busses/i2c-mv64xxx.c:904: undefined reference to `reset_control_assert' drivers/i2c/busses/i2c-mv64xxx.c:771: undefined reference to `devm_reset_control_get' drivers/i2c/busses/i2c-mv64xxx.c:778: undefined reference to `reset_control_deassert'
mv78xx0_defconfig: kernel/irq/Kconfig:41:error: recursive dependency detected! drivers/i2c/busses/i2c-mv64xxx.c:924: undefined reference to `reset_control_assert' drivers/i2c/busses/i2c-mv64xxx.c:904: undefined reference to `reset_control_assert'
mvebu_v5_defconfig: kernel/irq/Kconfig:41:error: recursive dependency detected! drivers/i2c/busses/i2c-mv64xxx.c:924: undefined reference to `reset_control_assert' drivers/i2c/busses/i2c-mv64xxx.c:904: undefined reference to `reset_control_assert' drivers/i2c/busses/i2c-mv64xxx.c:771: undefined reference to `devm_reset_control_get' drivers/i2c/busses/i2c-mv64xxx.c:778: undefined reference to `reset_control_deassert'
mvebu_v7_defconfig: kernel/irq/Kconfig:41:error: recursive dependency detected! drivers/i2c/busses/i2c-mv64xxx.c:924: undefined reference to `reset_control_assert' drivers/i2c/busses/i2c-mv64xxx.c:904: undefined reference to `reset_control_assert' drivers/i2c/busses/i2c-mv64xxx.c:771: undefined reference to `devm_reset_control_get' drivers/i2c/busses/i2c-mv64xxx.c:778: undefined reference to `reset_control_deassert'
orion5x_defconfig: kernel/irq/Kconfig:41:error: recursive dependency detected! drivers/i2c/busses/i2c-mv64xxx.c:924: undefined reference to `reset_control_assert' drivers/i2c/busses/i2c-mv64xxx.c:904: undefined reference to `reset_control_assert' drivers/i2c/busses/i2c-mv64xxx.c:771: undefined reference to `devm_reset_control_get' drivers/i2c/busses/i2c-mv64xxx.c:778: undefined reference to `reset_control_deassert'
Warnings: 1 drivers/gpio/gpio-pl061.c:358:2: warning: format '%x' expects argument of type 'unsigned int', but argument 3 has type 'resource_size_t' [-Wformat=] 1 drivers/irqchip/irq-bcm2835.c:201:1: warning: 'externally_visible' attribute have effect only on public objects [-Wattributes] 1 drivers/irqchip/irq-bcm2835.c:99:9: warning: 'externally_visible' attribute have effect only on public objects [-Wattributes] 1 drivers/irqchip/irq-clps711x.c:78:1: warning: 'externally_visible' attribute have effect only on public objects [-Wattributes] 1 drivers/irqchip/irq-moxart.c:48:1: warning: 'externally_visible' attribute have effect only on public objects [-Wattributes] 1 drivers/usb/host/xhci-plat.c:203:12: warning: 'xhci_plat_suspend' defined but not used [-Wunused-function] 1 drivers/usb/host/xhci-plat.c:211:12: warning: 'xhci_plat_resume' defined but not used [-Wunused-function] 2 buildall.arm.multi_lpae_defconfig.log.passed:warning: (ARM_HIGHBANK_CPUFREQ) selects GENERIC_CPUFREQ_CPU0 which has unmet direct dependencies (ARCH_HAS_CPUFREQ && CPU_FREQ && HAVE_CLK && REGULATOR && OF && THERMAL && CPU_THERMAL) 2 buildall.arm.multi_v7_defconfig.log.passed:warning: (ARM_HIGHBANK_CPUFREQ) selects GENERIC_CPUFREQ_CPU0 which has unmet direct dependencies (ARCH_HAS_CPUFREQ && CPU_FREQ && HAVE_CLK && REGULATOR && OF && THERMAL && CPU_THERMAL) 3 drivers/irqchip/irq-mmp.c:199:1: warning: 'externally_visible' attribute have effect only on public objects [-Wattributes] 3 drivers/irqchip/irq-mmp.c:212:1: warning: 'externally_visible' attribute have effect only on public objects [-Wattributes] 3 drivers/irqchip/irq-orion.c:35:1: warning: 'externally_visible' attribute have effect only on public objects [-Wattributes] 3 drivers/irqchip/irq-sirfsoc.c:51:1: warning: 'externally_visible' attribute have effect only on public objects [-Wattributes] 3 drivers/irqchip/irq-sun4i.c:140:1: warning: 'externally_visible' attribute have effect only on public objects [-Wattributes] 3 drivers/irqchip/irq-sun4i.c:39:70: warning: 'externally_visible' attribute have effect only on public objects [-Wattributes] 3 drivers/irqchip/irq-vt8500.c:183:1: warning: 'externally_visible' attribute have effect only on public objects [-Wattributes] 5 drivers/irqchip/irq-armada-370-xp.c:415:1: warning: 'externally_visible' attribute have effect only on public objects [-Wattributes] 13 drivers/irqchip/irq-vic.c:244:1: warning: 'externally_visible' attribute have effect only on public objects [-Wattributes] 28 drivers/irqchip/irq-gic.c:283:1: warning: 'externally_visible' attribute have effect only on public objects [-Wattributes]
Section mismatches: 1 integrator_defconfig WARNING: arch/arm/mach-integrator/built-in.o(.data+0x2e0): Section mismatch in reference from the variable impd1_driver to the function .init.text:impd1_probe() 1 integrator_defconfig WARNING: vmlinux.o(.data+0x1ba0): Section mismatch in reference from the variable impd1_driver to the function .init.text:impd1_probe() 1 multi_lpae_defconfig WARNING: drivers/built-in.o(.data+0x5125c): Section mismatch in reference from the variable socfpga_child_clocks to the function .init.text:socfpga_pll_init() 1 multi_lpae_defconfig WARNING: drivers/built-in.o(.data+0x51320): Section mismatch in reference from the variable socfpga_child_clocks to the function .init.text:socfpga_periph_init() 1 multi_lpae_defconfig WARNING: drivers/built-in.o(.data+0x513e4): Section mismatch in reference from the variable socfpga_child_clocks to the function .init.text:socfpga_gate_init() 1 multi_lpae_defconfig WARNING: drivers/clk/built-in.o(.data+0xbc94): Section mismatch in reference from the variable socfpga_child_clocks to the function .init.text:socfpga_pll_init() 1 multi_lpae_defconfig WARNING: drivers/clk/built-in.o(.data+0xbd58): Section mismatch in reference from the variable socfpga_child_clocks to the function .init.text:socfpga_periph_init() 1 multi_lpae_defconfig WARNING: drivers/clk/built-in.o(.data+0xbe1c): Section mismatch in reference from the variable socfpga_child_clocks to the function .init.text:socfpga_gate_init() 1 multi_lpae_defconfig WARNING: drivers/clk/socfpga/built-in.o(.data+0x184): Section mismatch in reference from the variable socfpga_child_clocks to the function .init.text:socfpga_periph_init() 1 multi_lpae_defconfig WARNING: drivers/clk/socfpga/built-in.o(.data+0x248): Section mismatch in reference from the variable socfpga_child_clocks to the function .init.text:socfpga_gate_init() 1 multi_lpae_defconfig WARNING: drivers/clk/socfpga/built-in.o(.data+0xc0): Section mismatch in reference from the variable socfpga_child_clocks to the function .init.text:socfpga_pll_init() 1 multi_lpae_defconfig WARNING: vmlinux.o(.data+0x98a1c): Section mismatch in reference from the variable socfpga_child_clocks to the function .init.text:socfpga_pll_init() 1 multi_lpae_defconfig WARNING: vmlinux.o(.data+0x98ae0): Section mismatch in reference from the variable socfpga_child_clocks to the function .init.text:socfpga_periph_init() 1 multi_lpae_defconfig WARNING: vmlinux.o(.data+0x98ba4): Section mismatch in reference from the variable socfpga_child_clocks to the function .init.text:socfpga_gate_init() 1 multi_v7_defconfig WARNING: drivers/built-in.o(.data+0x50ddc): Section mismatch in reference from the variable socfpga_child_clocks to the function .init.text:socfpga_pll_init() 1 multi_v7_defconfig WARNING: drivers/built-in.o(.data+0x50ea0): Section mismatch in reference from the variable socfpga_child_clocks to the function .init.text:socfpga_periph_init() 1 multi_v7_defconfig WARNING: drivers/built-in.o(.data+0x50f64): Section mismatch in reference from the variable socfpga_child_clocks to the function .init.text:socfpga_gate_init() 1 multi_v7_defconfig WARNING: drivers/clk/built-in.o(.data+0xbc94): Section mismatch in reference from the variable socfpga_child_clocks to the function .init.text:socfpga_pll_init() 1 multi_v7_defconfig WARNING: drivers/clk/built-in.o(.data+0xbd58): Section mismatch in reference from the variable socfpga_child_clocks to the function .init.text:socfpga_periph_init() 1 multi_v7_defconfig WARNING: drivers/clk/built-in.o(.data+0xbe1c): Section mismatch in reference from the variable socfpga_child_clocks to the function .init.text:socfpga_gate_init() 1 multi_v7_defconfig WARNING: drivers/clk/socfpga/built-in.o(.data+0x184): Section mismatch in reference from the variable socfpga_child_clocks to the function .init.text:socfpga_periph_init() 1 multi_v7_defconfig WARNING: drivers/clk/socfpga/built-in.o(.data+0x248): Section mismatch in reference from the variable socfpga_child_clocks to the function .init.text:socfpga_gate_init() 1 multi_v7_defconfig WARNING: drivers/clk/socfpga/built-in.o(.data+0xc0): Section mismatch in reference from the variable socfpga_child_clocks to the function .init.text:socfpga_pll_init() 1 multi_v7_defconfig WARNING: vmlinux.o(.data+0x9805c): Section mismatch in reference from the variable socfpga_child_clocks to the function .init.text:socfpga_pll_init() 1 multi_v7_defconfig WARNING: vmlinux.o(.data+0x98120): Section mismatch in reference from the variable socfpga_child_clocks to the function .init.text:socfpga_periph_init() 1 multi_v7_defconfig WARNING: vmlinux.o(.data+0x981e4): Section mismatch in reference from the variable socfpga_child_clocks to the function .init.text:socfpga_gate_init() 1 socfpga_defconfig WARNING: drivers/built-in.o(.data+0x855c): Section mismatch in reference from the variable socfpga_child_clocks to the function .init.text:socfpga_pll_init() 1 socfpga_defconfig WARNING: drivers/built-in.o(.data+0x8620): Section mismatch in reference from the variable socfpga_child_clocks to the function .init.text:socfpga_periph_init() 1 socfpga_defconfig WARNING: drivers/built-in.o(.data+0x86e4): Section mismatch in reference from the variable socfpga_child_clocks to the function .init.text:socfpga_gate_init() 1 socfpga_defconfig WARNING: drivers/clk/built-in.o(.data+0x164): Section mismatch in reference from the variable socfpga_child_clocks to the function .init.text:socfpga_pll_init() 1 socfpga_defconfig WARNING: drivers/clk/built-in.o(.data+0x228): Section mismatch in reference from the variable socfpga_child_clocks to the function .init.text:socfpga_periph_init() 1 socfpga_defconfig WARNING: drivers/clk/built-in.o(.data+0x2ec): Section mismatch in reference from the variable socfpga_child_clocks to the function .init.text:socfpga_gate_init() 1 socfpga_defconfig WARNING: drivers/clk/socfpga/built-in.o(.data+0x184): Section mismatch in reference from the variable socfpga_child_clocks to the function .init.text:socfpga_periph_init() 1 socfpga_defconfig WARNING: drivers/clk/socfpga/built-in.o(.data+0x248): Section mismatch in reference from the variable socfpga_child_clocks to the function .init.text:socfpga_gate_init() 1 socfpga_defconfig WARNING: drivers/clk/socfpga/built-in.o(.data+0xc0): Section mismatch in reference from the variable socfpga_child_clocks to the function .init.text:socfpga_pll_init() 1 socfpga_defconfig WARNING: vmlinux.o(.data+0x15d04): Section mismatch in reference from the variable socfpga_child_clocks to the function .init.text:socfpga_pll_init() 1 socfpga_defconfig WARNING: vmlinux.o(.data+0x15dc8): Section mismatch in reference from the variable socfpga_child_clocks to the function .init.text:socfpga_periph_init() 1 socfpga_defconfig WARNING: vmlinux.o(.data+0x15e8c): Section mismatch in reference from the variable socfpga_child_clocks to the function .init.text:socfpga_gate_init()
Wolfram,
On Thu, Mar 06, 2014 at 10:46:45PM -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:
1b0a7e3 Add linux-next specific files for 20140307
Build logs (stderr only) can be found at the following link (experimental):
http://arm-soc.lixom.net/buildlogs/next/next-20140307/
Runtime: 45m 24s
Passed: 116 Failed: 9
Warnings: 78
Section mismatches: 38
Failed defconfigs: dove_defconfig ebsa110_defconfig efm32_defconfig kirkwood_defconfig multi_v5_defconfig mv78xx0_defconfig mvebu_v5_defconfig mvebu_v7_defconfig orion5x_defconfig
Errors:
dove_defconfig: kernel/irq/Kconfig:41:error: recursive dependency detected! drivers/i2c/busses/i2c-mv64xxx.c:924: undefined reference to `reset_control_assert' drivers/i2c/busses/i2c-mv64xxx.c:904: undefined reference to `reset_control_assert'
...
kirkwood_defconfig: kernel/irq/Kconfig:41:error: recursive dependency detected! drivers/i2c/busses/i2c-mv64xxx.c:924: undefined reference to `reset_control_assert' drivers/i2c/busses/i2c-mv64xxx.c:904: undefined reference to `reset_control_assert' drivers/i2c/busses/i2c-mv64xxx.c:771: undefined reference to `devm_reset_control_get' drivers/i2c/busses/i2c-mv64xxx.c:778: undefined reference to `reset_control_deassert'
multi_v5_defconfig: kernel/irq/Kconfig:41:error: recursive dependency detected! drivers/i2c/busses/i2c-mv64xxx.c:924: undefined reference to `reset_control_assert' drivers/i2c/busses/i2c-mv64xxx.c:904: undefined reference to `reset_control_assert' drivers/i2c/busses/i2c-mv64xxx.c:771: undefined reference to `devm_reset_control_get' drivers/i2c/busses/i2c-mv64xxx.c:778: undefined reference to `reset_control_deassert'
mv78xx0_defconfig: kernel/irq/Kconfig:41:error: recursive dependency detected! drivers/i2c/busses/i2c-mv64xxx.c:924: undefined reference to `reset_control_assert' drivers/i2c/busses/i2c-mv64xxx.c:904: undefined reference to `reset_control_assert'
mvebu_v5_defconfig: kernel/irq/Kconfig:41:error: recursive dependency detected! drivers/i2c/busses/i2c-mv64xxx.c:924: undefined reference to `reset_control_assert' drivers/i2c/busses/i2c-mv64xxx.c:904: undefined reference to `reset_control_assert' drivers/i2c/busses/i2c-mv64xxx.c:771: undefined reference to `devm_reset_control_get' drivers/i2c/busses/i2c-mv64xxx.c:778: undefined reference to `reset_control_deassert'
mvebu_v7_defconfig: kernel/irq/Kconfig:41:error: recursive dependency detected! drivers/i2c/busses/i2c-mv64xxx.c:924: undefined reference to `reset_control_assert' drivers/i2c/busses/i2c-mv64xxx.c:904: undefined reference to `reset_control_assert' drivers/i2c/busses/i2c-mv64xxx.c:771: undefined reference to `devm_reset_control_get' drivers/i2c/busses/i2c-mv64xxx.c:778: undefined reference to `reset_control_deassert'
orion5x_defconfig: kernel/irq/Kconfig:41:error: recursive dependency detected! drivers/i2c/busses/i2c-mv64xxx.c:924: undefined reference to `reset_control_assert' drivers/i2c/busses/i2c-mv64xxx.c:904: undefined reference to `reset_control_assert' drivers/i2c/busses/i2c-mv64xxx.c:771: undefined reference to `devm_reset_control_get' drivers/i2c/busses/i2c-mv64xxx.c:778: undefined reference to `reset_control_deassert'
I do believe I saw a fix for this, is it in the pipe?
thx,
Jason.
Wolfram,
resent to the correct address for Wolfram. aliases updated. Sorry for the extra noise.
On Thu, Mar 06, 2014 at 10:46:45PM -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:
1b0a7e3 Add linux-next specific files for 20140307
Build logs (stderr only) can be found at the following link (experimental):
http://arm-soc.lixom.net/buildlogs/next/next-20140307/
Runtime: 45m 24s
Passed: 116 Failed: 9
Warnings: 78
Section mismatches: 38
Failed defconfigs: dove_defconfig ebsa110_defconfig efm32_defconfig kirkwood_defconfig multi_v5_defconfig mv78xx0_defconfig mvebu_v5_defconfig mvebu_v7_defconfig orion5x_defconfig
Errors:
dove_defconfig: kernel/irq/Kconfig:41:error: recursive dependency detected! drivers/i2c/busses/i2c-mv64xxx.c:924: undefined reference to `reset_control_assert' drivers/i2c/busses/i2c-mv64xxx.c:904: undefined reference to `reset_control_assert'
...
kirkwood_defconfig: kernel/irq/Kconfig:41:error: recursive dependency detected! drivers/i2c/busses/i2c-mv64xxx.c:924: undefined reference to `reset_control_assert' drivers/i2c/busses/i2c-mv64xxx.c:904: undefined reference to `reset_control_assert' drivers/i2c/busses/i2c-mv64xxx.c:771: undefined reference to `devm_reset_control_get' drivers/i2c/busses/i2c-mv64xxx.c:778: undefined reference to `reset_control_deassert'
multi_v5_defconfig: kernel/irq/Kconfig:41:error: recursive dependency detected! drivers/i2c/busses/i2c-mv64xxx.c:924: undefined reference to `reset_control_assert' drivers/i2c/busses/i2c-mv64xxx.c:904: undefined reference to `reset_control_assert' drivers/i2c/busses/i2c-mv64xxx.c:771: undefined reference to `devm_reset_control_get' drivers/i2c/busses/i2c-mv64xxx.c:778: undefined reference to `reset_control_deassert'
mv78xx0_defconfig: kernel/irq/Kconfig:41:error: recursive dependency detected! drivers/i2c/busses/i2c-mv64xxx.c:924: undefined reference to `reset_control_assert' drivers/i2c/busses/i2c-mv64xxx.c:904: undefined reference to `reset_control_assert'
mvebu_v5_defconfig: kernel/irq/Kconfig:41:error: recursive dependency detected! drivers/i2c/busses/i2c-mv64xxx.c:924: undefined reference to `reset_control_assert' drivers/i2c/busses/i2c-mv64xxx.c:904: undefined reference to `reset_control_assert' drivers/i2c/busses/i2c-mv64xxx.c:771: undefined reference to `devm_reset_control_get' drivers/i2c/busses/i2c-mv64xxx.c:778: undefined reference to `reset_control_deassert'
mvebu_v7_defconfig: kernel/irq/Kconfig:41:error: recursive dependency detected! drivers/i2c/busses/i2c-mv64xxx.c:924: undefined reference to `reset_control_assert' drivers/i2c/busses/i2c-mv64xxx.c:904: undefined reference to `reset_control_assert' drivers/i2c/busses/i2c-mv64xxx.c:771: undefined reference to `devm_reset_control_get' drivers/i2c/busses/i2c-mv64xxx.c:778: undefined reference to `reset_control_deassert'
orion5x_defconfig: kernel/irq/Kconfig:41:error: recursive dependency detected! drivers/i2c/busses/i2c-mv64xxx.c:924: undefined reference to `reset_control_assert' drivers/i2c/busses/i2c-mv64xxx.c:904: undefined reference to `reset_control_assert' drivers/i2c/busses/i2c-mv64xxx.c:771: undefined reference to `devm_reset_control_get' drivers/i2c/busses/i2c-mv64xxx.c:778: undefined reference to `reset_control_deassert'
I do believe I saw a fix for this, is it in the pipe?
thx,
Jason.
I do believe I saw a fix for this, is it in the pipe?
It is being worked on: https://lkml.org/lkml/2014/3/7/252
I don't like adding #ifdef, though :(
On Fri, Mar 07, 2014 at 09:01:23AM -0500, Jason Cooper wrote:
Wolfram,
resent to the correct address for Wolfram. aliases updated. Sorry for the extra noise.
On Thu, Mar 06, 2014 at 10:46:45PM -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:
1b0a7e3 Add linux-next specific files for 20140307
Build logs (stderr only) can be found at the following link (experimental):
http://arm-soc.lixom.net/buildlogs/next/next-20140307/
Runtime: 45m 24s
Passed: 116 Failed: 9
Warnings: 78
Section mismatches: 38
Failed defconfigs: dove_defconfig ebsa110_defconfig efm32_defconfig kirkwood_defconfig multi_v5_defconfig mv78xx0_defconfig mvebu_v5_defconfig mvebu_v7_defconfig orion5x_defconfig
Errors:
dove_defconfig: kernel/irq/Kconfig:41:error: recursive dependency detected! drivers/i2c/busses/i2c-mv64xxx.c:924: undefined reference to `reset_control_assert' drivers/i2c/busses/i2c-mv64xxx.c:904: undefined reference to `reset_control_assert'
...
kirkwood_defconfig: kernel/irq/Kconfig:41:error: recursive dependency detected! drivers/i2c/busses/i2c-mv64xxx.c:924: undefined reference to `reset_control_assert' drivers/i2c/busses/i2c-mv64xxx.c:904: undefined reference to `reset_control_assert' drivers/i2c/busses/i2c-mv64xxx.c:771: undefined reference to `devm_reset_control_get' drivers/i2c/busses/i2c-mv64xxx.c:778: undefined reference to `reset_control_deassert'
multi_v5_defconfig: kernel/irq/Kconfig:41:error: recursive dependency detected! drivers/i2c/busses/i2c-mv64xxx.c:924: undefined reference to `reset_control_assert' drivers/i2c/busses/i2c-mv64xxx.c:904: undefined reference to `reset_control_assert' drivers/i2c/busses/i2c-mv64xxx.c:771: undefined reference to `devm_reset_control_get' drivers/i2c/busses/i2c-mv64xxx.c:778: undefined reference to `reset_control_deassert'
mv78xx0_defconfig: kernel/irq/Kconfig:41:error: recursive dependency detected! drivers/i2c/busses/i2c-mv64xxx.c:924: undefined reference to `reset_control_assert' drivers/i2c/busses/i2c-mv64xxx.c:904: undefined reference to `reset_control_assert'
mvebu_v5_defconfig: kernel/irq/Kconfig:41:error: recursive dependency detected! drivers/i2c/busses/i2c-mv64xxx.c:924: undefined reference to `reset_control_assert' drivers/i2c/busses/i2c-mv64xxx.c:904: undefined reference to `reset_control_assert' drivers/i2c/busses/i2c-mv64xxx.c:771: undefined reference to `devm_reset_control_get' drivers/i2c/busses/i2c-mv64xxx.c:778: undefined reference to `reset_control_deassert'
mvebu_v7_defconfig: kernel/irq/Kconfig:41:error: recursive dependency detected! drivers/i2c/busses/i2c-mv64xxx.c:924: undefined reference to `reset_control_assert' drivers/i2c/busses/i2c-mv64xxx.c:904: undefined reference to `reset_control_assert' drivers/i2c/busses/i2c-mv64xxx.c:771: undefined reference to `devm_reset_control_get' drivers/i2c/busses/i2c-mv64xxx.c:778: undefined reference to `reset_control_deassert'
orion5x_defconfig: kernel/irq/Kconfig:41:error: recursive dependency detected! drivers/i2c/busses/i2c-mv64xxx.c:924: undefined reference to `reset_control_assert' drivers/i2c/busses/i2c-mv64xxx.c:904: undefined reference to `reset_control_assert' drivers/i2c/busses/i2c-mv64xxx.c:771: undefined reference to `devm_reset_control_get' drivers/i2c/busses/i2c-mv64xxx.c:778: undefined reference to `reset_control_deassert'
I do believe I saw a fix for this, is it in the pipe?
These build problems have been present for over 10 days now - what's happening to get them fixed?
On Tue, Mar 18, 2014 at 10:15:55AM +0000, Russell King - ARM Linux wrote:
On Fri, Mar 07, 2014 at 09:01:23AM -0500, Jason Cooper wrote:
Wolfram,
resent to the correct address for Wolfram. aliases updated. Sorry for the extra noise.
On Thu, Mar 06, 2014 at 10:46:45PM -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:
1b0a7e3 Add linux-next specific files for 20140307
Build logs (stderr only) can be found at the following link (experimental):
http://arm-soc.lixom.net/buildlogs/next/next-20140307/
Runtime: 45m 24s
Passed: 116 Failed: 9
Warnings: 78
Section mismatches: 38
Failed defconfigs: dove_defconfig ebsa110_defconfig efm32_defconfig kirkwood_defconfig multi_v5_defconfig mv78xx0_defconfig mvebu_v5_defconfig mvebu_v7_defconfig orion5x_defconfig
Errors:
dove_defconfig: kernel/irq/Kconfig:41:error: recursive dependency detected! drivers/i2c/busses/i2c-mv64xxx.c:924: undefined reference to `reset_control_assert' drivers/i2c/busses/i2c-mv64xxx.c:904: undefined reference to `reset_control_assert'
...
kirkwood_defconfig: kernel/irq/Kconfig:41:error: recursive dependency detected! drivers/i2c/busses/i2c-mv64xxx.c:924: undefined reference to `reset_control_assert' drivers/i2c/busses/i2c-mv64xxx.c:904: undefined reference to `reset_control_assert' drivers/i2c/busses/i2c-mv64xxx.c:771: undefined reference to `devm_reset_control_get' drivers/i2c/busses/i2c-mv64xxx.c:778: undefined reference to `reset_control_deassert'
multi_v5_defconfig: kernel/irq/Kconfig:41:error: recursive dependency detected! drivers/i2c/busses/i2c-mv64xxx.c:924: undefined reference to `reset_control_assert' drivers/i2c/busses/i2c-mv64xxx.c:904: undefined reference to `reset_control_assert' drivers/i2c/busses/i2c-mv64xxx.c:771: undefined reference to `devm_reset_control_get' drivers/i2c/busses/i2c-mv64xxx.c:778: undefined reference to `reset_control_deassert'
mv78xx0_defconfig: kernel/irq/Kconfig:41:error: recursive dependency detected! drivers/i2c/busses/i2c-mv64xxx.c:924: undefined reference to `reset_control_assert' drivers/i2c/busses/i2c-mv64xxx.c:904: undefined reference to `reset_control_assert'
mvebu_v5_defconfig: kernel/irq/Kconfig:41:error: recursive dependency detected! drivers/i2c/busses/i2c-mv64xxx.c:924: undefined reference to `reset_control_assert' drivers/i2c/busses/i2c-mv64xxx.c:904: undefined reference to `reset_control_assert' drivers/i2c/busses/i2c-mv64xxx.c:771: undefined reference to `devm_reset_control_get' drivers/i2c/busses/i2c-mv64xxx.c:778: undefined reference to `reset_control_deassert'
mvebu_v7_defconfig: kernel/irq/Kconfig:41:error: recursive dependency detected! drivers/i2c/busses/i2c-mv64xxx.c:924: undefined reference to `reset_control_assert' drivers/i2c/busses/i2c-mv64xxx.c:904: undefined reference to `reset_control_assert' drivers/i2c/busses/i2c-mv64xxx.c:771: undefined reference to `devm_reset_control_get' drivers/i2c/busses/i2c-mv64xxx.c:778: undefined reference to `reset_control_deassert'
orion5x_defconfig: kernel/irq/Kconfig:41:error: recursive dependency detected! drivers/i2c/busses/i2c-mv64xxx.c:924: undefined reference to `reset_control_assert' drivers/i2c/busses/i2c-mv64xxx.c:904: undefined reference to `reset_control_assert' drivers/i2c/busses/i2c-mv64xxx.c:771: undefined reference to `devm_reset_control_get' drivers/i2c/busses/i2c-mv64xxx.c:778: undefined reference to `reset_control_deassert'
I do believe I saw a fix for this, is it in the pipe?
These build problems have been present for over 10 days now - what's happening to get them fixed?
I sent a patch last monday to fix those that hasn't been merged yet. http://lists.infradead.org/pipermail/linux-arm-kernel/2014-March/239069.html
These build problems have been present for over 10 days now - what's happening to get them fixed?
I sent a patch last monday to fix those that hasn't been merged yet. http://lists.infradead.org/pipermail/linux-arm-kernel/2014-March/239069.html
The dependency for this patch is sadly not in linux-next so far. CCing Phillip.
Am Montag, den 24.03.2014, 14:37 +0100 schrieb Wolfram Sang:
These build problems have been present for over 10 days now - what's happening to get them fixed?
I sent a patch last monday to fix those that hasn't been merged yet. http://lists.infradead.org/pipermail/linux-arm-kernel/2014-March/239069.html
The dependency for this patch is sadly not in linux-next so far. CCing Phillip.
It is part of this pull request:
http://lists.infradead.org/pipermail/linux-arm-kernel/2014-March/241459.html
regards Philipp
On Mon, Mar 24, 2014 at 03:26:26PM +0100, Philipp Zabel wrote:
Am Montag, den 24.03.2014, 14:37 +0100 schrieb Wolfram Sang:
These build problems have been present for over 10 days now - what's happening to get them fixed?
I sent a patch last monday to fix those that hasn't been merged yet. http://lists.infradead.org/pipermail/linux-arm-kernel/2014-March/239069.html
The dependency for this patch is sadly not in linux-next so far. CCing Phillip.
It is part of this pull request:
http://lists.infradead.org/pipermail/linux-arm-kernel/2014-March/241459.html
Do you have a branch in linux-next?
thx,
Jason.
kernel-build-reports@lists.linaro.org