Re: linux-next: Tree for Jul 30 [build failure on arm64]

2020-07-31 Thread Stephen Rothwell
Hi Christoph, On Fri, 31 Jul 2020 11:00:22 +0200 Christoph Hellwig wrote: > > Please just drop the branch for now. I will revert those 4 commits from today's linux-next and all Al needs to do is reset his for-next branch to its parent. -- Cheers, Stephen Rothwell pgptop3INTvLv.pgp

Re: linux-next: Tree for Jul 30 [build failure on arm64]

2020-07-31 Thread Christoph Hellwig
Ok, looks like my baseline had arm64 defconfig fail due to a missing include already, so the script didn't see a regression due to the existing failure in ptrauth_keys_init_user. Looks like moving the definіtion to asm-generic/compat.h is a better idea better anyway.

Re: linux-next: Tree for Jul 30 [build failure on arm64]

2020-07-31 Thread Christoph Hellwig
Please just drop the branch for now.

Re: linux-next: Tree for Jul 30 [build failure on arm64]

2020-07-31 Thread Shaokun Zhang
Hi, 在 2020/7/31 16:30, Naresh Kamboju 写道: > On Fri, 31 Jul 2020 at 09:38, Stephen Rothwell wrote: >> >> Hi all, >> >> On Fri, 31 Jul 2020 10:46:52 +0800 Shaokun Zhang >> wrote: >>> >>> There's a build failure on arm64: >>> >>> In file included from ./include/linux/compat.h:17:0, >>>

Re: linux-next: Tree for Jul 30 [build failure on arm64]

2020-07-31 Thread Stephen Rothwell
Hi Naresh, On Fri, 31 Jul 2020 14:00:57 +0530 Naresh Kamboju wrote: > > > Presumably caused by commit > > > > b902bfb3f0e9 ("arm64: stop using directly") > > I have reverted this commit > b902bfb3f0e9 ("arm64: stop using directly") > > and rebuilt arm64 failed due to below

Re: linux-next: Tree for Jul 30 [build failure on arm64]

2020-07-31 Thread Naresh Kamboju
On Fri, 31 Jul 2020 at 09:38, Stephen Rothwell wrote: > > Hi all, > > On Fri, 31 Jul 2020 10:46:52 +0800 Shaokun Zhang > wrote: > > > > There's a build failure on arm64: > > > > In file included from ./include/linux/compat.h:17:0, > > from ./arch/arm64/include/asm/stat.h:13, >

Re: linux-next: Tree for Jul 30 [build failure on arm64]

2020-07-30 Thread Stephen Rothwell
Hi all, On Fri, 31 Jul 2020 10:46:52 +0800 Shaokun Zhang wrote: > > There's a build failure on arm64: > > In file included from ./include/linux/compat.h:17:0, > from ./arch/arm64/include/asm/stat.h:13, > from ./include/linux/stat.h:6, > from

Re: linux-next: Tree for Jul 30 [build failure on arm64]

2020-07-30 Thread Shaokun Zhang
Hi, There's a build failure on arm64: In file included from ./include/linux/compat.h:17:0, from ./arch/arm64/include/asm/stat.h:13, from ./include/linux/stat.h:6, from ./include/linux/sysfs.h:22, from

linux-next: Tree for Jul 30

2020-07-30 Thread Stephen Rothwell
Hi all, Changes since 20200729: My fixes tree contains: dbf24e30ce2e ("device_cgroup: Fix RCU list debugging warning") Linus' tree gained a build failure for which I revertd a commit. The vfs tree lost its build failure. The printk tree lost its build failure. The net-next tree lost its

Re: linux-next: Tree for Jul 30 (drivers/net/phy/mdio-octeon.c: i386)

2019-07-30 Thread Randy Dunlap
On 7/29/19 10:15 PM, Stephen Rothwell wrote: > Hi all, > > Changes since 20190729: > on i386: ../drivers/net/phy/mdio-octeon.c: In function ‘octeon_mdiobus_probe’: ../drivers/net/phy/mdio-octeon.c:48:3: warning: cast from pointer to integer of different size [-Wpointer-to-int-cast]

linux-next: Tree for Jul 30

2019-07-29 Thread Stephen Rothwell
Hi all, Changes since 20190729: New tree: fsverity The keys tree gained a semantic conflict against the fsverity tree for which I applied a merge fix patch. Non-merge commits (relative to Linus' tree): 2756 3095 files changed, 191869 insertions(+), 78406 deletions(-)

linux-next: Tree for Jul 30

2018-07-30 Thread Stephen Rothwell
Hi all, Changes since 20180727: Undropped tree: kspp The v4l-dvb tree lost its build failure. The net-next tree lost its build failure. The crypto tree gained a conflict against the net-mext tree. The devicetree tree gained a conflict against the net-next tree. The xen-tip tree gained a

linux-next: Tree for Jul 30

2018-07-30 Thread Stephen Rothwell
Hi all, Changes since 20180727: Undropped tree: kspp The v4l-dvb tree lost its build failure. The net-next tree lost its build failure. The crypto tree gained a conflict against the net-mext tree. The devicetree tree gained a conflict against the net-next tree. The xen-tip tree gained a

linux-next: Tree for Jul 30

2015-07-30 Thread Stephen Rothwell
Hi all, Changes since 20150729: The nfsd tree gained a conflict against Linus' tree. The net-next tree gained a conflict against the net tree. The drm-misc tree gained a conflict against Linus' tree. The block tree gained conflicts against the ext3 and f2fs trees and a build failure for which

linux-next: Tree for Jul 30

2015-07-30 Thread Stephen Rothwell
Hi all, Changes since 20150729: The nfsd tree gained a conflict against Linus' tree. The net-next tree gained a conflict against the net tree. The drm-misc tree gained a conflict against Linus' tree. The block tree gained conflicts against the ext3 and f2fs trees and a build failure for which

linux-next: Tree for Jul 30

2014-07-30 Thread Stephen Rothwell
Hi all, Changes since 20140729: The net tree gained a build failure so I used the version from next-20140729. The pm tree gained a conflict against the arm-soc tree. The modules tree still had its build failure so I used the version from next-20140725. The mmc-uh tree still had its build

linux-next: Tree for Jul 30

2014-07-30 Thread Stephen Rothwell
Hi all, Changes since 20140729: The net tree gained a build failure so I used the version from next-20140729. The pm tree gained a conflict against the arm-soc tree. The modules tree still had its build failure so I used the version from next-20140725. The mmc-uh tree still had its build

linux-next: Tree for Jul 30

2013-07-30 Thread Stephen Rothwell
Hi all, Changes since 20130729: The ext4 tree still has its build failure so I used the version from next-20130726. The next-next tree lost its build failure but gained another for which I reverted a commit. The spi tree lost its build failure. The usb-gadget tree gained a conflict against

linux-next: Tree for Jul 30

2013-07-30 Thread Stephen Rothwell
Hi all, Changes since 20130729: The ext4 tree still has its build failure so I used the version from next-20130726. The next-next tree lost its build failure but gained another for which I reverted a commit. The spi tree lost its build failure. The usb-gadget tree gained a conflict against