linux-next: Tree for Nov 17

2020-11-16 Thread Stephen Rothwell
Hi all, Changes since 20201116: The amdgpu tree gained a conflict against the drm tree. The phy-next tree gained a build failure so I used the version from next-20201116. The mhi tree gained a build failure so I used the version from next-20201116. The akpm-current tree gained a conflict again

linux-next: Tree for Nov 17

2017-11-16 Thread Stephen Rothwell
Hi all, Please do not add any v4.16 material to your linux-next included trees until v4.15-rc1 has been released. Changes since 20171116: The vfs tree gained a conflict against Linus' tree. Non-merge commits (relative to Linus' tree): 3321 2505 files changed, 198683 insertions(+), 31988 deleti

Re: linux-next: Tree for Nov 17

2016-11-18 Thread Paul Gortmaker
On Thu, Nov 17, 2016 at 1:08 AM, Stephen Rothwell wrote: > Hi all, > > There will be no linux-next releases on Friday (tomorrow) or Monday. > > Changes since 20161116: FYI, I saw this warning appear today (make allmodconfig; multi arch) drivers/remoteproc/Kconfig:3:error: recursive dependency de

linux-next: Tree for Nov 17

2016-11-16 Thread Stephen Rothwell
Hi all, There will be no linux-next releases on Friday (tomorrow) or Monday. Changes since 20161116: The net-next tree gained conflicts against the net tree. The drm tree gained a conflict against the arm tree. The block tree gained conflicts against the btrfs-kdave tree. The tip tree gained

linux-next: Tree for Nov 17

2015-11-16 Thread Stephen Rothwell
Hi all, Changes since 20151116: Unropped tree: target-merge Non-merge commits (relative to Linus' tree): 1472 1114 files changed, 60028 insertions(+), 22781 deletions(-) I have created today's linux-next tree at git:

linux-next: Tree for Nov 17

2014-11-17 Thread Stephen Rothwell
Hi all, Changes since 20141114: The idle tree gained a conflict against the pm tree. The net-next tree gained a build failure for which I applied a merge fix patch. The drm tree gained conflicts against the drm-intel-fixes and Linus' trees. The block tree gained a build failure so I used the v