Re: linux-next: Tree for May 13 (drivers/pinctrl/pinctrl-stmfx)

2019-05-13 Thread Randy Dunlap
On 5/13/19 8:06 AM, Randy Dunlap wrote: > On 5/12/19 9:25 PM, Stephen Rothwell wrote: >> Hi all, >> >> Please do not add any v5.3 material to your linux-next included >> trees/branches until after v5.2-rc1 has been released. >> >> Changes since 20190510: >> > > on x86_64: > # CONFIG_OF is not set

Re: linux-next: Tree for May 13 (drivers/pinctrl/pinctrl-stmfx)

2019-05-13 Thread Randy Dunlap
On 5/12/19 9:25 PM, Stephen Rothwell wrote: > Hi all, > > Please do not add any v5.3 material to your linux-next included > trees/branches until after v5.2-rc1 has been released. > > Changes since 20190510: > on x86_64: # CONFIG_OF is not set ../drivers/pinctrl/pinctrl-stmfx.c:410:20: error:

linux-next: Tree for May 13

2019-05-12 Thread Stephen Rothwell
Hi all, Please do not add any v5.3 material to your linux-next included trees/branches until after v5.2-rc1 has been released. Changes since 20190510: The mips tree gained a conflict against Linus' tree. The thermal-soc tree gained a conflict against Linus' tree and a build failure for which I

linux-next: Tree for May 13

2016-05-12 Thread Stephen Rothwell
Hi all, Changes since 20160512: Dropped tree: rdma-leon (bad build and conflicts) The rdma-leon tree gained a build failure so I dropped it for today. The staging tree gained a build failure for which I applied a merge fix patch. The pinctrl tree lost its build failure. Non-merge commits (rel

Re: linux-next: Tree for May 13 (avr32 build error due to switchdev patch)

2015-05-13 Thread Guenter Roeck
On Wed, May 13, 2015 at 06:09:27PM +1000, Stephen Rothwell wrote: > Hi all, > > Changes since 20150512: > > New tree: h8300 > > The net-next tree gained a conflict against the net tree. > > The security tree gained conflicts against the vfs tree. > > The spi tree lost its build failure. > > T

linux-next: Tree for May 13

2015-05-13 Thread Stephen Rothwell
Hi all, Changes since 20150512: New tree: h8300 The net-next tree gained a conflict against the net tree. The security tree gained conflicts against the vfs tree. The spi tree lost its build failure. The target-updates tree still had its build failure so I used the version from next-20150511.

Re: linux-next: Tree for May 13

2014-05-13 Thread Stephen Rothwell
Hi all, On Tue, 13 May 2014 18:16:51 +1000 Stephen Rothwell wrote: > > Non-merge commits (relative to Linus' tree): 4501 > 4211 files changed, 151888 insertions(+), 93171 deletions(-) Actually: Non-merge commits (relative to Linus' tree): 4960 4638 files changed, 174648 insertions(+), 10761

linux-next: Tree for May 13

2014-05-13 Thread Stephen Rothwell
Hi all, Changes since 20140512: My fixes tree contains: powerpc/ppc64: Allow allmodconfig to build (finally !) The powerpc tree gained a conflict against the fixes tree. The fsl tree lost its build failure. The vfs tree gained a conflict against the cifs tree. The net-next tree gained

linux-next: Tree for May 13

2013-05-12 Thread Stephen Rothwell
Hi all, Changes since 20130510: The akpm tree gained a conflict against Linus' tree. I have created today's linux-next tree at git://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git (patches at http://www.ke