linux-next: Tree for May 31

Hi all, Changes since 20190530: The net-next tree gained a conflict against the net tree. It also gained a build failure for which I reverted a commit. I applied a patch to fix an sh build probem. The akpm-current tree lost its build failure. Non-merge commits (relative to Linus' tree): 3342

linux-next: Tree for May 31

Hi all, Changes since 20180530: The kbuild tree lost its build failure. The powerpc tree gained a conflict against the kbuild tree. The net-next tree still had its build failure for which I reverted 3 commits. The crypto tree lost its build failures. The device-mapper tree gained a build

linux-next: Tree for May 31

Hi all, Changes since 20180530: The kbuild tree lost its build failure. The powerpc tree gained a conflict against the kbuild tree. The net-next tree still had its build failure for which I reverted 3 commits. The crypto tree lost its build failures. The device-mapper tree gained a build

Re: linux-next: Tree for May 31

Stephen Rothwell writes: > Hi Michael, > > On Thu, 01 Jun 2017 16:07:51 +1000 Michael Ellerman > wrote: >> >> Stephen Rothwell writes: >> >> > Changes since 20170530: >> > >> > Non-merge commits (relative to Linus' tree):

Re: linux-next: Tree for May 31

Stephen Rothwell writes: > Hi Michael, > > On Thu, 01 Jun 2017 16:07:51 +1000 Michael Ellerman > wrote: >> >> Stephen Rothwell writes: >> >> > Changes since 20170530: >> > >> > Non-merge commits (relative to Linus' tree): 3325 >> > 3598 files changed, 135000 insertions(+), 72065

Re: linux-next: Tree for May 31

Michael Ellerman writes: > Stephen Rothwell writes: > >> Hi all, >> >> Changes since 20170530: >> >> The mfd tree gained a build failure so I used the version from >> next-20170530. >> >> The drivers-x86 tree gained the same build failure as the mfd

Re: linux-next: Tree for May 31

Michael Ellerman writes: > Stephen Rothwell writes: > >> Hi all, >> >> Changes since 20170530: >> >> The mfd tree gained a build failure so I used the version from >> next-20170530. >> >> The drivers-x86 tree gained the same build failure as the mfd tree so >> I used the version from

Re: linux-next: Tree for May 31

Hi Michael, On Thu, 01 Jun 2017 16:07:51 +1000 Michael Ellerman wrote: > > Stephen Rothwell writes: > > > Changes since 20170530: > > > > Non-merge commits (relative to Linus' tree): 3325 > > 3598 files changed, 135000 insertions(+), 72065

Re: linux-next: Tree for May 31

Hi Michael, On Thu, 01 Jun 2017 16:07:51 +1000 Michael Ellerman wrote: > > Stephen Rothwell writes: > > > Changes since 20170530: > > > > Non-merge commits (relative to Linus' tree): 3325 > > 3598 files changed, 135000 insertions(+), 72065 deletions(-) > > More or less all my powerpc boxes

Re: linux-next: Tree for May 31

Stephen Rothwell writes: > Hi all, > > Changes since 20170530: > > The mfd tree gained a build failure so I used the version from > next-20170530. > > The drivers-x86 tree gained the same build failure as the mfd tree so > I used the version from next-20170530. > > The rtc

Re: linux-next: Tree for May 31

Stephen Rothwell writes: > Hi all, > > Changes since 20170530: > > The mfd tree gained a build failure so I used the version from > next-20170530. > > The drivers-x86 tree gained the same build failure as the mfd tree so > I used the version from next-20170530. > > The rtc tree gained a build

linux-next: Tree for May 31

Hi all, Changes since 20170530: The mfd tree gained a build failure so I used the version from next-20170530. The drivers-x86 tree gained the same build failure as the mfd tree so I used the version from next-20170530. The rtc tree gained a build failure so I used the version from

linux-next: Tree for May 31

Hi all, Changes since 20170530: The mfd tree gained a build failure so I used the version from next-20170530. The drivers-x86 tree gained the same build failure as the mfd tree so I used the version from next-20170530. The rtc tree gained a build failure so I used the version from

linux-next: Tree for May 31

Hi all, Changes since 20160530: My fixes tree contains: of: silence warnings due to max() usage The drm-intel tree gained conflicts against Linus' tree. Non-merge commits (relative to Linus' tree): 946 788 files changed, 26579 insertions(+), 12133 deletions(-)

linux-next: Tree for May 31

Hi all, Changes since 20160530: My fixes tree contains: of: silence warnings due to max() usage The drm-intel tree gained conflicts against Linus' tree. Non-merge commits (relative to Linus' tree): 946 788 files changed, 26579 insertions(+), 12133 deletions(-)

linux-next: Tree for May 31

Hi all, Changes since 20130530: The msm tree gained a build failure for which I applied a fix patch. I have created today's linux-next tree at git://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git (patches

linux-next: Tree for May 31

Hi all, Changes since 20130530: The msm tree gained a build failure for which I applied a fix patch. I have created today's linux-next tree at git://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git (patches