next-20160104 build: 3 failures 15 warnings (next-20160104)

next-20160104 build: 3 failures 15 warnings (next-20160104)

[Build bot for Mark Brown]

Tree/Branch: next-20160104
Git describe: next-20160104
Commit: 57c4229929 Add linux-next specific files for 20160104

Build Time: 65 min 8 sec

Passed:    6 / 9   ( 66.67 %)
Failed:    3 / 9   ( 33.33 %)

Errors: 1
Warnings: 15
Section Mismatches: 0

Failed defconfigs:
	arm64-allmodconfig
	arm-allmodconfig
	arm64-defconfig

Errors:

	arm64-allmodconfig
Error: ../arch/arm64/boot/dts/mediatek/mt8173.dtsi:132.24-25 syntax error
Error: ../arch/arm64/boot/dts/mediatek/mt8173.dtsi:132.24-25 syntax error

	arm64-defconfig
Error: ../arch/arm64/boot/dts/mediatek/mt8173.dtsi:132.24-25 syntax error

-------------------------------------------------------------------------------
defconfigs with issues (other than build errors):
      3 warnings    0 mismatches  : arm64-allnoconfig
      5 warnings    0 mismatches  : arm64-allmodconfig
      7 warnings    0 mismatches  : arm-multi_v5_defconfig
      9 warnings    0 mismatches  : arm-multi_v7_defconfig
      7 warnings    0 mismatches  : arm-allmodconfig
      4 warnings    0 mismatches  : arm-allnoconfig
      4 warnings    0 mismatches  : arm64-defconfig

-------------------------------------------------------------------------------

Errors summary: 1
	  3 Error: ../arch/arm64/boot/dts/mediatek/mt8173.dtsi:132.24-25 syntax error

Warnings Summary: 15
	  7 ../mm/page_alloc.c:4617:37: warning: unused variable 'tmp' [-Wunused-variable]
	  7 ../mm/page_alloc.c:4617:26: warning: unused variable 'r' [-Wunused-variable]
	  6 <stdin>:1307:2: warning: #warning syscall copy_file_range not implemented [-Wcpp]
	  4 ../mm/page_alloc.c:5276:25: warning: 'zone_start_pfn' may be used uninitialized in this function [-Wuninitialized]
	  4 ../drivers/tty/serial/amba-pl011.c:190:27: warning: 'vendor_zte' defined but not used [-Wunused-variable]
	  2 ../mm/page_alloc.c:5276:25: warning: 'zone_start_pfn' may be used uninitialized in this function [-Wmaybe-uninitialized]
	  1 arch/arm/configs/multi_v7_defconfig:435:warning: symbol value 'm' invalid for MFD_DA9063
	  1 ../net/bluetooth/mgmt.c:5471:8: warning: 'r192' may be used uninitialized in this function [-Wmaybe-uninitialized]
	  1 ../net/bluetooth/mgmt.c:5471:8: warning: 'h192' may be used uninitialized in this function [-Wmaybe-uninitialized]
	  1 ../fs/udf/inode.c:1974:3: warning: 'adsize' may be used uninitialized in this function [-Wmaybe-uninitialized]
	  1 ../fs/udf/inode.c:1927:28: warning: 'adsize' may be used uninitialized in this function [-Wmaybe-uninitialized]
	  1 ../fs/dax.c:916:17: warning: passing argument 1 of '__dax_dbg' from incompatible pointer type
	  1 ../drivers/gpu/drm/vc4/vc4_validate.c:864:4: warning: format '%d' expects argument of type 'int', but argument 4 has type 'size_t' [-Wformat=]
	  1 ../drivers/gpu/drm/amd/amdgpu/../powerplay/hwmgr/ppevvmath.h:382:5: warning: comparison of distinct pointer types lacks a cast [enabled by default]
	  1 ../crypto/wp512.c:987:1: warning: the frame size of 1112 bytes is larger than 1024 bytes [-Wframe-larger-than=]



===============================================================================
Detailed per-defconfig build reports below:


-------------------------------------------------------------------------------
arm64-allnoconfig : PASS, 0 errors, 3 warnings, 0 section mismatches

Warnings:
	../mm/page_alloc.c:4617:37: warning: unused variable 'tmp' [-Wunused-variable]
	../mm/page_alloc.c:4617:26: warning: unused variable 'r' [-Wunused-variable]
	../mm/page_alloc.c:5276:25: warning: 'zone_start_pfn' may be used uninitialized in this function [-Wmaybe-uninitialized]

-------------------------------------------------------------------------------
arm64-allmodconfig : FAIL, 2 errors, 5 warnings, 0 section mismatches

Errors:
	Error: ../arch/arm64/boot/dts/mediatek/mt8173.dtsi:132.24-25 syntax error
	Error: ../arch/arm64/boot/dts/mediatek/mt8173.dtsi:132.24-25 syntax error

Warnings:
	../mm/page_alloc.c:4617:37: warning: unused variable 'tmp' [-Wunused-variable]
	../mm/page_alloc.c:4617:26: warning: unused variable 'r' [-Wunused-variable]
	../fs/dax.c:916:17: warning: passing argument 1 of '__dax_dbg' from incompatible pointer type
	../drivers/gpu/drm/vc4/vc4_validate.c:864:4: warning: format '%d' expects argument of type 'int', but argument 4 has type 'size_t' [-Wformat=]
	../drivers/tty/serial/amba-pl011.c:190:27: warning: 'vendor_zte' defined but not used [-Wunused-variable]

-------------------------------------------------------------------------------
arm-multi_v5_defconfig : PASS, 0 errors, 7 warnings, 0 section mismatches

Warnings:
	<stdin>:1307:2: warning: #warning syscall copy_file_range not implemented [-Wcpp]
	../mm/page_alloc.c:4617:37: warning: unused variable 'tmp' [-Wunused-variable]
	../mm/page_alloc.c:4617:26: warning: unused variable 'r' [-Wunused-variable]
	../mm/page_alloc.c:5276:25: warning: 'zone_start_pfn' may be used uninitialized in this function [-Wuninitialized]
	../fs/udf/inode.c:1974:3: warning: 'adsize' may be used uninitialized in this function [-Wmaybe-uninitialized]
	../fs/udf/inode.c:1927:28: warning: 'adsize' may be used uninitialized in this function [-Wmaybe-uninitialized]
	<stdin>:1307:2: warning: #warning syscall copy_file_range not implemented [-Wcpp]

-------------------------------------------------------------------------------
arm-multi_v7_defconfig : PASS, 0 errors, 9 warnings, 0 section mismatches

Warnings:
	arch/arm/configs/multi_v7_defconfig:435:warning: symbol value 'm' invalid for MFD_DA9063
	<stdin>:1307:2: warning: #warning syscall copy_file_range not implemented [-Wcpp]
	../mm/page_alloc.c:4617:37: warning: unused variable 'tmp' [-Wunused-variable]
	../mm/page_alloc.c:4617:26: warning: unused variable 'r' [-Wunused-variable]
	../mm/page_alloc.c:5276:25: warning: 'zone_start_pfn' may be used uninitialized in this function [-Wuninitialized]
	../net/bluetooth/mgmt.c:5471:8: warning: 'r192' may be used uninitialized in this function [-Wmaybe-uninitialized]
	../net/bluetooth/mgmt.c:5471:8: warning: 'h192' may be used uninitialized in this function [-Wmaybe-uninitialized]
	../drivers/tty/serial/amba-pl011.c:190:27: warning: 'vendor_zte' defined but not used [-Wunused-variable]
	<stdin>:1307:2: warning: #warning syscall copy_file_range not implemented [-Wcpp]

-------------------------------------------------------------------------------
arm-allmodconfig : FAIL, 0 errors, 7 warnings, 0 section mismatches

Warnings:
	<stdin>:1307:2: warning: #warning syscall copy_file_range not implemented [-Wcpp]
	../mm/page_alloc.c:4617:37: warning: unused variable 'tmp' [-Wunused-variable]
	../mm/page_alloc.c:4617:26: warning: unused variable 'r' [-Wunused-variable]
	../mm/page_alloc.c:5276:25: warning: 'zone_start_pfn' may be used uninitialized in this function [-Wuninitialized]
	../crypto/wp512.c:987:1: warning: the frame size of 1112 bytes is larger than 1024 bytes [-Wframe-larger-than=]
	../drivers/gpu/drm/amd/amdgpu/../powerplay/hwmgr/ppevvmath.h:382:5: warning: comparison of distinct pointer types lacks a cast [enabled by default]
	../drivers/tty/serial/amba-pl011.c:190:27: warning: 'vendor_zte' defined but not used [-Wunused-variable]

-------------------------------------------------------------------------------
arm-allnoconfig : PASS, 0 errors, 4 warnings, 0 section mismatches

Warnings:
	<stdin>:1307:2: warning: #warning syscall copy_file_range not implemented [-Wcpp]
	../mm/page_alloc.c:4617:37: warning: unused variable 'tmp' [-Wunused-variable]
	../mm/page_alloc.c:4617:26: warning: unused variable 'r' [-Wunused-variable]
	../mm/page_alloc.c:5276:25: warning: 'zone_start_pfn' may be used uninitialized in this function [-Wuninitialized]

-------------------------------------------------------------------------------
arm64-defconfig : FAIL, 1 errors, 4 warnings, 0 section mismatches

Errors:
	Error: ../arch/arm64/boot/dts/mediatek/mt8173.dtsi:132.24-25 syntax error

Warnings:
	../mm/page_alloc.c:4617:37: warning: unused variable 'tmp' [-Wunused-variable]
	../mm/page_alloc.c:4617:26: warning: unused variable 'r' [-Wunused-variable]
	../mm/page_alloc.c:5276:25: warning: 'zone_start_pfn' may be used uninitialized in this function [-Wmaybe-uninitialized]
	../drivers/tty/serial/amba-pl011.c:190:27: warning: 'vendor_zte' defined but not used [-Wunused-variable]
-------------------------------------------------------------------------------

Passed with no errors, warnings or mismatches:

x86_64-allnoconfig
x86_64-defconfig

Re: next-20160104 build: 3 failures 15 warnings (next-20160104)

[Mark Brown]

[-- Attachment #1: Type: text/plain, Size: 728 bytes --]

On Mon, Jan 04, 2016 at 12:12:20PM +0000, Build bot for Mark Brown wrote:

Today's linux-next fails to build for arm64 due to 44d3d051253 (ARM64:
dts: mt8173: Add CPU OPP, clock and regulator supply properties) in one
of Raphael's trees:

> 	arm64-allmodconfig
> Error: ../arch/arm64/boot/dts/mediatek/mt8173.dtsi:132.24-25 syntax error
> Error: ../arch/arm64/boot/dts/mediatek/mt8173.dtsi:132.24-25 syntax error

> 	arm64-defconfig
> Error: ../arch/arm64/boot/dts/mediatek/mt8173.dtsi:132.24-25 syntax error

which is failing because at least CLK_INFRA_CA53SEL is used but never
defined, presumably there is some dependency which wasn't integrated.
Normally we merge DT changes via the architecture to help avoid these
issues.

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 473 bytes --]

next-20160104 build: 3 failures 15 warnings (next-20160104)

[Mark Brown]

On Mon, Jan 04, 2016 at 12:12:20PM +0000, Build bot for Mark Brown wrote:

Today's linux-next fails to build for arm64 due to 44d3d051253 (ARM64:
dts: mt8173: Add CPU OPP, clock and regulator supply properties) in one
of Raphael's trees:

> 	arm64-allmodconfig
> Error: ../arch/arm64/boot/dts/mediatek/mt8173.dtsi:132.24-25 syntax error
> Error: ../arch/arm64/boot/dts/mediatek/mt8173.dtsi:132.24-25 syntax error

> 	arm64-defconfig
> Error: ../arch/arm64/boot/dts/mediatek/mt8173.dtsi:132.24-25 syntax error

which is failing because at least CLK_INFRA_CA53SEL is used but never
defined, presumably there is some dependency which wasn't integrated.
Normally we merge DT changes via the architecture to help avoid these
issues.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 473 bytes
Desc: not available
URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20160104/6ae7e456/attachment-0001.sig>

Re: next-20160104 build: 3 failures 15 warnings (next-20160104)

[Mark Brown]

[-- Attachment #1: Type: text/plain, Size: 1034 bytes --]

On Mon, Jan 04, 2016 at 12:12:20PM +0000, Build bot for Mark Brown wrote:

Today's linux-next fails to build an arm allmodconfig (and probably also
at least arm64 though other errors prevent that getting to linking
currently) due to:

| drivers/built-in.o: In function `dtsec_restart_autoneg':
| :(.text+0x30f86c): undefined reference to `mdiobus_read'
| :(.text+0x30f89c): undefined reference to `mdiobus_write'
| drivers/built-in.o: In function `dtsec_init':
| :(.text+0x31008c): undefined reference to `mdiobus_write'
| :(.text+0x3100b4): undefined reference to `mdiobus_write'
| :(.text+0x3100dc): undefined reference to `mdiobus_write'
| :(.text+0x310128): undefined reference to `mdiobus_write'
| drivers/built-in.o::(.text+0x310150): more undefined references to `mdiobus_write' follow
| drivers/built-in.o: In function `dtsec_config':
| :(.text+0x310804): undefined reference to `of_phy_find_device'

and various other linker errors caused by the fact that the new fman
driver uses PHYLIB but does not depend on or select it.

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 473 bytes --]

next-20160104 build: 3 failures 15 warnings (next-20160104)

[Mark Brown]

On Mon, Jan 04, 2016 at 12:12:20PM +0000, Build bot for Mark Brown wrote:

Today's linux-next fails to build an arm allmodconfig (and probably also
at least arm64 though other errors prevent that getting to linking
currently) due to:

| drivers/built-in.o: In function `dtsec_restart_autoneg':
| :(.text+0x30f86c): undefined reference to `mdiobus_read'
| :(.text+0x30f89c): undefined reference to `mdiobus_write'
| drivers/built-in.o: In function `dtsec_init':
| :(.text+0x31008c): undefined reference to `mdiobus_write'
| :(.text+0x3100b4): undefined reference to `mdiobus_write'
| :(.text+0x3100dc): undefined reference to `mdiobus_write'
| :(.text+0x310128): undefined reference to `mdiobus_write'
| drivers/built-in.o::(.text+0x310150): more undefined references to `mdiobus_write' follow
| drivers/built-in.o: In function `dtsec_config':
| :(.text+0x310804): undefined reference to `of_phy_find_device'

and various other linker errors caused by the fact that the new fman
driver uses PHYLIB but does not depend on or select it.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 473 bytes
Desc: not available
URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20160104/187e4c0e/attachment.sig>

Re: next-20160104 build: 3 failures 15 warnings (next-20160104)

[Arnd Bergmann]

On Monday 04 January 2016 16:50:25 Mark Brown wrote:
> On Mon, Jan 04, 2016 at 12:12:20PM +0000, Build bot for Mark Brown wrote:
> 
> Today's linux-next fails to build an arm allmodconfig (and probably also
> at least arm64 though other errors prevent that getting to linking
> currently) due to:
> 
> | drivers/built-in.o: In function `dtsec_restart_autoneg':
> | :(.text+0x30f86c): undefined reference to `mdiobus_read'
> | :(.text+0x30f89c): undefined reference to `mdiobus_write'
> | drivers/built-in.o: In function `dtsec_init':
> | :(.text+0x31008c): undefined reference to `mdiobus_write'
> | :(.text+0x3100b4): undefined reference to `mdiobus_write'
> | :(.text+0x3100dc): undefined reference to `mdiobus_write'
> | :(.text+0x310128): undefined reference to `mdiobus_write'
> | drivers/built-in.o::(.text+0x310150): more undefined references to `mdiobus_write' follow
> | drivers/built-in.o: In function `dtsec_config':
> | :(.text+0x310804): undefined reference to `of_phy_find_device'
> 
> and various other linker errors caused by the fact that the new fman
> driver uses PHYLIB but does not depend on or select it.

This is the patch I submitted for the problem. I don't think that simply
adding the 'select' would be a good idea because that would force PHYLIB
builtin for allmodconfig.

	Arnd

commit 609a5b98a4b703a4fba8becb7ffb2aa1859c4164
Author: Arnd Bergmann <arnd@arndb.de>
Date:   Fri Jan 1 13:24:03 2016 +0100

    [SUBMITTED] fsl/fman: allow modular build
    
    ARM allmodconfig fails because of the addition of the FMAN driver:
    
    drivers/built-in.o: In function `dtsec_restart_autoneg':
    binder.c:(.text+0x173328): undefined reference to `mdiobus_read'
    binder.c:(.text+0x173348): undefined reference to `mdiobus_write'
    drivers/built-in.o: In function `dtsec_config':
    binder.c:(.text+0x173d24): undefined reference to `of_phy_find_device'
    drivers/built-in.o: In function `init_phy':
    binder.c:(.text+0x1763b0): undefined reference to `of_phy_connect'
    drivers/built-in.o: In function `stop':
    binder.c:(.text+0x176014): undefined reference to `phy_stop'
    drivers/built-in.o: In function `start':
    binder.c:(.text+0x176078): undefined reference to `phy_start'
    
    The reason is that the driver uses PHYLIB, but that is a loadable
    module here, and fman itself is built-in.
    
    This patch makes it possible to configure fman as a module as well
    so we don't change the status of PHYLIB in an allmodconfig kernel,
    and it adds a 'select PHYLIB' statement to ensure that phylib is
    always built-in when fman is.
    
    The driver uses "builtin_platform_driver(fman_driver);", which means
    it cannot be unloaded, but it's still possible to have it as a loadable
    module that gets loaded once and never removed.
    
    Signed-off-by: Arnd Bergmann <arnd@arndb.de>
    Fixes: 5adae51a64b8 ("fsl/fman: Add FMan MURAM support")

diff --git a/drivers/net/ethernet/freescale/fman/Kconfig b/drivers/net/ethernet/freescale/fman/Kconfig
index 66b729692b48..79b7c84b7869 100644
--- a/drivers/net/ethernet/freescale/fman/Kconfig
+++ b/drivers/net/ethernet/freescale/fman/Kconfig
@@ -1,7 +1,8 @@
 config FSL_FMAN
-	bool "FMan support"
+	tristate "FMan support"
 	depends on FSL_SOC || COMPILE_TEST
 	select GENERIC_ALLOCATOR
+	select PHYLIB
 	default n
 	help
 		Freescale Data-Path Acceleration Architecture Frame Manager

next-20160104 build: 3 failures 15 warnings (next-20160104)

[Arnd Bergmann]

On Monday 04 January 2016 16:50:25 Mark Brown wrote:
> On Mon, Jan 04, 2016 at 12:12:20PM +0000, Build bot for Mark Brown wrote:
> 
> Today's linux-next fails to build an arm allmodconfig (and probably also
> at least arm64 though other errors prevent that getting to linking
> currently) due to:
> 
> | drivers/built-in.o: In function `dtsec_restart_autoneg':
> | :(.text+0x30f86c): undefined reference to `mdiobus_read'
> | :(.text+0x30f89c): undefined reference to `mdiobus_write'
> | drivers/built-in.o: In function `dtsec_init':
> | :(.text+0x31008c): undefined reference to `mdiobus_write'
> | :(.text+0x3100b4): undefined reference to `mdiobus_write'
> | :(.text+0x3100dc): undefined reference to `mdiobus_write'
> | :(.text+0x310128): undefined reference to `mdiobus_write'
> | drivers/built-in.o::(.text+0x310150): more undefined references to `mdiobus_write' follow
> | drivers/built-in.o: In function `dtsec_config':
> | :(.text+0x310804): undefined reference to `of_phy_find_device'
> 
> and various other linker errors caused by the fact that the new fman
> driver uses PHYLIB but does not depend on or select it.

This is the patch I submitted for the problem. I don't think that simply
adding the 'select' would be a good idea because that would force PHYLIB
builtin for allmodconfig.

	Arnd

commit 609a5b98a4b703a4fba8becb7ffb2aa1859c4164
Author: Arnd Bergmann <arnd@arndb.de>
Date:   Fri Jan 1 13:24:03 2016 +0100

    [SUBMITTED] fsl/fman: allow modular build
    
    ARM allmodconfig fails because of the addition of the FMAN driver:
    
    drivers/built-in.o: In function `dtsec_restart_autoneg':
    binder.c:(.text+0x173328): undefined reference to `mdiobus_read'
    binder.c:(.text+0x173348): undefined reference to `mdiobus_write'
    drivers/built-in.o: In function `dtsec_config':
    binder.c:(.text+0x173d24): undefined reference to `of_phy_find_device'
    drivers/built-in.o: In function `init_phy':
    binder.c:(.text+0x1763b0): undefined reference to `of_phy_connect'
    drivers/built-in.o: In function `stop':
    binder.c:(.text+0x176014): undefined reference to `phy_stop'
    drivers/built-in.o: In function `start':
    binder.c:(.text+0x176078): undefined reference to `phy_start'
    
    The reason is that the driver uses PHYLIB, but that is a loadable
    module here, and fman itself is built-in.
    
    This patch makes it possible to configure fman as a module as well
    so we don't change the status of PHYLIB in an allmodconfig kernel,
    and it adds a 'select PHYLIB' statement to ensure that phylib is
    always built-in when fman is.
    
    The driver uses "builtin_platform_driver(fman_driver);", which means
    it cannot be unloaded, but it's still possible to have it as a loadable
    module that gets loaded once and never removed.
    
    Signed-off-by: Arnd Bergmann <arnd@arndb.de>
    Fixes: 5adae51a64b8 ("fsl/fman: Add FMan MURAM support")

diff --git a/drivers/net/ethernet/freescale/fman/Kconfig b/drivers/net/ethernet/freescale/fman/Kconfig
index 66b729692b48..79b7c84b7869 100644
--- a/drivers/net/ethernet/freescale/fman/Kconfig
+++ b/drivers/net/ethernet/freescale/fman/Kconfig
@@ -1,7 +1,8 @@
 config FSL_FMAN
-	bool "FMan support"
+	tristate "FMan support"
 	depends on FSL_SOC || COMPILE_TEST
 	select GENERIC_ALLOCATOR
+	select PHYLIB
 	default n
 	help
 		Freescale Data-Path Acceleration Architecture Frame Manager

Re: next-20160104 build: 3 failures 15 warnings (next-20160104)

[Mark Brown]

[-- Attachment #1: Type: text/plain, Size: 634 bytes --]

On Mon, Jan 04, 2016 at 11:07:41PM +0100, Arnd Bergmann wrote:
> On Monday 04 January 2016 16:50:25 Mark Brown wrote:
> > On Mon, Jan 04, 2016 at 12:12:20PM +0000, Build bot for Mark Brown wrote:

> > and various other linker errors caused by the fact that the new fman
> > driver uses PHYLIB but does not depend on or select it.

> This is the patch I submitted for the problem. I don't think that simply
> adding the 'select' would be a good idea because that would force PHYLIB
> builtin for allmodconfig.

Indeed, that was why I held off on my own patch - I wanted to go back
and try to understand why we were using a bool there.

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 473 bytes --]

next-20160104 build: 3 failures 15 warnings (next-20160104)

[Mark Brown]

On Mon, Jan 04, 2016 at 11:07:41PM +0100, Arnd Bergmann wrote:
> On Monday 04 January 2016 16:50:25 Mark Brown wrote:
> > On Mon, Jan 04, 2016 at 12:12:20PM +0000, Build bot for Mark Brown wrote:

> > and various other linker errors caused by the fact that the new fman
> > driver uses PHYLIB but does not depend on or select it.

> This is the patch I submitted for the problem. I don't think that simply
> adding the 'select' would be a good idea because that would force PHYLIB
> builtin for allmodconfig.

Indeed, that was why I held off on my own patch - I wanted to go back
and try to understand why we were using a bool there.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 473 bytes
Desc: not available
URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20160104/8dd9e541/attachment.sig>

Re: next-20160104 build: 3 failures 15 warnings (next-20160104)

[Rafael J. Wysocki]

On 1/4/2016 4:35 PM, Mark Brown wrote:
> On Mon, Jan 04, 2016 at 12:12:20PM +0000, Build bot for Mark Brown wrote:
>
> Today's linux-next fails to build for arm64 due to 44d3d051253 (ARM64:
> dts: mt8173: Add CPU OPP, clock and regulator supply properties)

Thanks for letting me know, I've dropped this one.

> in one of Raphael's trees:
>
>> 	arm64-allmodconfig
>> Error: ../arch/arm64/boot/dts/mediatek/mt8173.dtsi:132.24-25 syntax error
>> Error: ../arch/arm64/boot/dts/mediatek/mt8173.dtsi:132.24-25 syntax error
>> 	arm64-defconfig
>> Error: ../arch/arm64/boot/dts/mediatek/mt8173.dtsi:132.24-25 syntax error
> which is failing because at least CLK_INFRA_CA53SEL is used but never
> defined, presumably there is some dependency which wasn't integrated.
> Normally we merge DT changes via the architecture to help avoid these
> issues.

Yes, that would be better.

Thanks,
Rafael

next-20160104 build: 3 failures 15 warnings (next-20160104)

[Rafael J. Wysocki]

On 1/4/2016 4:35 PM, Mark Brown wrote:
> On Mon, Jan 04, 2016 at 12:12:20PM +0000, Build bot for Mark Brown wrote:
>
> Today's linux-next fails to build for arm64 due to 44d3d051253 (ARM64:
> dts: mt8173: Add CPU OPP, clock and regulator supply properties)

Thanks for letting me know, I've dropped this one.

> in one of Raphael's trees:
>
>> 	arm64-allmodconfig
>> Error: ../arch/arm64/boot/dts/mediatek/mt8173.dtsi:132.24-25 syntax error
>> Error: ../arch/arm64/boot/dts/mediatek/mt8173.dtsi:132.24-25 syntax error
>> 	arm64-defconfig
>> Error: ../arch/arm64/boot/dts/mediatek/mt8173.dtsi:132.24-25 syntax error
> which is failing because at least CLK_INFRA_CA53SEL is used but never
> defined, presumably there is some dependency which wasn't integrated.
> Normally we merge DT changes via the architecture to help avoid these
> issues.

Yes, that would be better.

Thanks,
Rafael