linux-next: Tree for Sep 4

2019-09-04 Thread Stephen Rothwell
Hi all, News: this will be the last linux-next I will release until Sept 30. Changes since 20190903: The regulator tree lost its build failure. The net-next tree gained a build failure due to an interaction with the kbuild tree for which I applied a patch. The drm tree gained conflicts

linux-next: Tree for Sep 4

2018-09-03 Thread Stephen Rothwell
Hi all, Changes since 20180903: Dropped trees: xarray, ida (temporarily) The dmi tree gained a conflict against Linus' tree. The net-next tree still had its build failure for which I reverted a commit. Non-merge commits (relative to Linus' tree): 1638 1936 files changed, 60594 insertions(+),

linux-next: Tree for Sep 4

2018-09-03 Thread Stephen Rothwell
Hi all, Changes since 20180903: Dropped trees: xarray, ida (temporarily) The dmi tree gained a conflict against Linus' tree. The net-next tree still had its build failure for which I reverted a commit. Non-merge commits (relative to Linus' tree): 1638 1936 files changed, 60594 insertions(+),

linux-next: Tree for Sep 4

2017-09-04 Thread Stephen Rothwell
Hi all, Changes since 20170901: The s390 tree gained a conflict against Linus' tree. The block tree gained a conflict against Linus' tree. The tip tree gained a conflict against the mips tree. The usb tree gained a conflict against the mips tree. The nvdimm tree gained a build failure for

linux-next: Tree for Sep 4

2017-09-04 Thread Stephen Rothwell
Hi all, Changes since 20170901: The s390 tree gained a conflict against Linus' tree. The block tree gained a conflict against Linus' tree. The tip tree gained a conflict against the mips tree. The usb tree gained a conflict against the mips tree. The nvdimm tree gained a build failure for

Re: linux-next: Tree for Sep 4 (netfilter: xt_TPROXY)

2013-09-04 Thread Florian Westphal
Randy Dunlap wrote: > On 09/04/13 01:13, Stephen Rothwell wrote: > > Hi all, > > > > Please do not add any code for v3.13 to your linux-next included branches > > until after v3.12-rc1 is released. > > > > Changes since 20130902: > > > > on x86_64: > > when CONFIG_IPV6=m > and

Re: linux-next: Tree for Sep 4 (netfilter: xt_TPROXY)

2013-09-04 Thread Randy Dunlap
On 09/04/13 01:13, Stephen Rothwell wrote: > Hi all, > > Please do not add any code for v3.13 to your linux-next included branches > until after v3.12-rc1 is released. > > Changes since 20130902: > on x86_64: when CONFIG_IPV6=m and CONFIG_NETFILTER_XT_TARGET_TPROXY=y: net/built-in.o: In

linux-next: Tree for Sep 4

2013-09-04 Thread Stephen Rothwell
Hi all, Please do not add any code for v3.13 to your linux-next included branches until after v3.12-rc1 is released. Changes since 20130902: The arm tree still had its build failure. The net-next tree lost its build failure. The tip tree gained s conflict against Linus' tree.

linux-next: Tree for Sep 4

2013-09-04 Thread Stephen Rothwell
Hi all, Please do not add any code for v3.13 to your linux-next included branches until after v3.12-rc1 is released. Changes since 20130902: The arm tree still had its build failure. The net-next tree lost its build failure. The tip tree gained s conflict against Linus' tree.

Re: linux-next: Tree for Sep 4 (netfilter: xt_TPROXY)

2013-09-04 Thread Randy Dunlap
On 09/04/13 01:13, Stephen Rothwell wrote: Hi all, Please do not add any code for v3.13 to your linux-next included branches until after v3.12-rc1 is released. Changes since 20130902: on x86_64: when CONFIG_IPV6=m and CONFIG_NETFILTER_XT_TARGET_TPROXY=y: net/built-in.o: In function

Re: linux-next: Tree for Sep 4 (netfilter: xt_TPROXY)

2013-09-04 Thread Florian Westphal
Randy Dunlap rdun...@infradead.org wrote: On 09/04/13 01:13, Stephen Rothwell wrote: Hi all, Please do not add any code for v3.13 to your linux-next included branches until after v3.12-rc1 is released. Changes since 20130902: on x86_64: when CONFIG_IPV6=m and