linux-next: Tree for Oct 9

2020-10-09 Thread Stephen Rothwell
Hi all, Changes since 20201008: The tip tree gained a build failure for which I reverted a commit series. The rcu tree gained a conflict agsinst the tip tree. The kspp tree gained a conflict agsinst Linus' tree. The xarray tree lost its build failures. Non-merge commits (relative to Linus'

linux-next: Tree for Oct 9

2019-10-08 Thread Stephen Rothwell
Hi all, Changes since 20191008: The bpf-next tree gained a conflict against the bpf tree. The drm-misc tree gained conflicts against the drm tree and a semantic conflict against the amdgpu tree. The staging tree lost its build failure. Non-merge commits (relative to Linus' tree): 3142 3370

Re: linux-next: Tree for Oct 9

2018-10-09 Thread Guenter Roeck
On Tue, Oct 09, 2018 at 07:02:34PM +1100, Stephen Rothwell wrote: > Hi all, > > Changes since 20181008: > > The s390 tree gained a conflict against the compiler-attributes tree. > > The ext4 tree gained a build failure for which I reverted a commit. > > The nfsd tree lost its build failure. >

Re: linux-next: Tree for Oct 9

2018-10-09 Thread Guenter Roeck
On Tue, Oct 09, 2018 at 07:02:34PM +1100, Stephen Rothwell wrote: > Hi all, > > Changes since 20181008: > > The s390 tree gained a conflict against the compiler-attributes tree. > > The ext4 tree gained a build failure for which I reverted a commit. > > The nfsd tree lost its build failure. >

Re: linux-next: Tree for Oct 9 (fs/proc/vmcore.c)

2018-10-09 Thread Randy Dunlap
On 10/9/18 1:02 AM, Stephen Rothwell wrote: > Hi all, > > Changes since 20181008: > on i386: fs/proc/vmcore.o: In function `read_from_oldmem.part.4': vmcore.c:(.text+0x14f): undefined reference to `copy_oldmem_page_encrypted' Full randconfig file is attached. -- ~Randy # # Automatically

Re: linux-next: Tree for Oct 9 (fs/proc/vmcore.c)

2018-10-09 Thread Randy Dunlap
On 10/9/18 1:02 AM, Stephen Rothwell wrote: > Hi all, > > Changes since 20181008: > on i386: fs/proc/vmcore.o: In function `read_from_oldmem.part.4': vmcore.c:(.text+0x14f): undefined reference to `copy_oldmem_page_encrypted' Full randconfig file is attached. -- ~Randy # # Automatically

Re: linux-next: Tree for Oct 9 (net/mpls/af_mpls.c)

2018-10-09 Thread Randy Dunlap
On 10/9/18 1:02 AM, Stephen Rothwell wrote: > Hi all, > > Changes since 20181008: > on i386: net/mpls/af_mpls.o: In function `mpls_dump_routes': af_mpls.c:(.text+0x15e5): undefined reference to `ip_valid_fib_dump_req' Full randconfig file is attached. -- ~Randy # # Automatically generated

Re: linux-next: Tree for Oct 9 (net/mpls/af_mpls.c)

2018-10-09 Thread Randy Dunlap
On 10/9/18 1:02 AM, Stephen Rothwell wrote: > Hi all, > > Changes since 20181008: > on i386: net/mpls/af_mpls.o: In function `mpls_dump_routes': af_mpls.c:(.text+0x15e5): undefined reference to `ip_valid_fib_dump_req' Full randconfig file is attached. -- ~Randy # # Automatically generated

linux-next: Tree for Oct 9

2018-10-09 Thread Stephen Rothwell
Hi all, Changes since 20181008: The s390 tree gained a conflict against the compiler-attributes tree. The ext4 tree gained a build failure for which I reverted a commit. The nfsd tree lost its build failure. The crypto tree lost its build failure. The net-next tree gained a conflict against

linux-next: Tree for Oct 9

2018-10-09 Thread Stephen Rothwell
Hi all, Changes since 20181008: The s390 tree gained a conflict against the compiler-attributes tree. The ext4 tree gained a build failure for which I reverted a commit. The nfsd tree lost its build failure. The crypto tree lost its build failure. The net-next tree gained a conflict against

Re: linux-next: Tree for Oct 9 (bluetooth/bpa10x.c)

2015-10-09 Thread Marcel Holtmann
Hi Randy, >> Changes since 20151008: >> > > on i386: > > warning: (BT_HCIBPA10X) selects BT_HCIUART_H4 which has unmet direct > dependencies (NET && BT && BT_HCIUART) > > drivers/built-in.o: In function `bpa10x_rx_complete': > bpa10x.c:(.text+0x2ac5e2): undefined reference to `h4_recv_buf'

Re: linux-next: Tree for Oct 9 (bluetooth/bpa10x.c)

2015-10-09 Thread Randy Dunlap
On 10/08/15 23:24, Stephen Rothwell wrote: > Hi all, > > Changes since 20151008: > on i386: warning: (BT_HCIBPA10X) selects BT_HCIUART_H4 which has unmet direct dependencies (NET && BT && BT_HCIUART) drivers/built-in.o: In function `bpa10x_rx_complete': bpa10x.c:(.text+0x2ac5e2): undefined

linux-next: Tree for Oct 9

2015-10-09 Thread Stephen Rothwell
Hi all, Changes since 20151008: My fixes tree contains: "perf tools: Fix build break on powerpc due to sample_reg_masks" "word-at-a-time.h: powerpc: implement define zero_bytemask" I used the h8300 tree from next-20150828 since the current tree has been rebased onto linux-next

linux-next: Tree for Oct 9

2015-10-09 Thread Stephen Rothwell
Hi all, Changes since 20151008: My fixes tree contains: "perf tools: Fix build break on powerpc due to sample_reg_masks" "word-at-a-time.h: powerpc: implement define zero_bytemask" I used the h8300 tree from next-20150828 since the current tree has been rebased onto linux-next

Re: linux-next: Tree for Oct 9 (bluetooth/bpa10x.c)

2015-10-09 Thread Marcel Holtmann
Hi Randy, >> Changes since 20151008: >> > > on i386: > > warning: (BT_HCIBPA10X) selects BT_HCIUART_H4 which has unmet direct > dependencies (NET && BT && BT_HCIUART) > > drivers/built-in.o: In function `bpa10x_rx_complete': > bpa10x.c:(.text+0x2ac5e2): undefined reference to `h4_recv_buf'

Re: linux-next: Tree for Oct 9 (bluetooth/bpa10x.c)

2015-10-09 Thread Randy Dunlap
On 10/08/15 23:24, Stephen Rothwell wrote: > Hi all, > > Changes since 20151008: > on i386: warning: (BT_HCIBPA10X) selects BT_HCIUART_H4 which has unmet direct dependencies (NET && BT && BT_HCIUART) drivers/built-in.o: In function `bpa10x_rx_complete': bpa10x.c:(.text+0x2ac5e2): undefined

linux-next: Tree for Oct 9

2014-10-09 Thread Stephen Rothwell
Hi all, Please do not add any material intended for v3.19 to your linux-next included trees until after v3.18-rc1 has been released. Changes since 20141008: Removed tree: dmaengine The tip tree gained a conflict against the mips tree. The percpu gained a conflict against the tip tree.

linux-next: Tree for Oct 9

2014-10-09 Thread Stephen Rothwell
Hi all, Please do not add any material intended for v3.19 to your linux-next included trees until after v3.18-rc1 has been released. Changes since 20141008: Removed tree: dmaengine The tip tree gained a conflict against the mips tree. The percpu gained a conflict against the tip tree.

Re: linux-next: Tree for Oct 9

2013-10-09 Thread Guenter Roeck
On Wed, Oct 09, 2013 at 08:44:24AM -0700, Guenter Roeck wrote: > On Wed, Oct 09, 2013 at 08:29:06AM -0700, Guenter Roeck wrote: > > On Wed, Oct 09, 2013 at 04:14:22PM +0200, Thierry Reding wrote: > > > Hi all, > > > > > > I've uploaded today's linux-next tree to the master branch of the > > >

Re: linux-next: Tree for Oct 9

2013-10-09 Thread Guenter Roeck
On Wed, Oct 09, 2013 at 08:29:06AM -0700, Guenter Roeck wrote: > On Wed, Oct 09, 2013 at 04:14:22PM +0200, Thierry Reding wrote: > > Hi all, > > > > I've uploaded today's linux-next tree to the master branch of the > > repository below: > > > >

Re: linux-next: Tree for Oct 9

2013-10-09 Thread Guenter Roeck
On Wed, Oct 09, 2013 at 04:14:22PM +0200, Thierry Reding wrote: > Hi all, > > I've uploaded today's linux-next tree to the master branch of the > repository below: > > git://gitorious.org/thierryreding/linux-next.git > > A next-20131009 tag is also provided for convenience. > > Gained

linux-next: Tree for Oct 9

2013-10-09 Thread Thierry Reding
Hi all, I've uploaded today's linux-next tree to the master branch of the repository below: git://gitorious.org/thierryreding/linux-next.git A next-20131009 tag is also provided for convenience. Gained a few conflicts, but nothing too exciting. x86, ARM, PowerPC and MIPS default

linux-next: Tree for Oct 9

2013-10-09 Thread Thierry Reding
Hi all, I've uploaded today's linux-next tree to the master branch of the repository below: git://gitorious.org/thierryreding/linux-next.git A next-20131009 tag is also provided for convenience. Gained a few conflicts, but nothing too exciting. x86, ARM, PowerPC and MIPS default

Re: linux-next: Tree for Oct 9

2013-10-09 Thread Guenter Roeck
On Wed, Oct 09, 2013 at 04:14:22PM +0200, Thierry Reding wrote: Hi all, I've uploaded today's linux-next tree to the master branch of the repository below: git://gitorious.org/thierryreding/linux-next.git A next-20131009 tag is also provided for convenience. Gained a few

Re: linux-next: Tree for Oct 9

2013-10-09 Thread Guenter Roeck
On Wed, Oct 09, 2013 at 08:29:06AM -0700, Guenter Roeck wrote: On Wed, Oct 09, 2013 at 04:14:22PM +0200, Thierry Reding wrote: Hi all, I've uploaded today's linux-next tree to the master branch of the repository below: git://gitorious.org/thierryreding/linux-next.git A

Re: linux-next: Tree for Oct 9

2013-10-09 Thread Guenter Roeck
On Wed, Oct 09, 2013 at 08:44:24AM -0700, Guenter Roeck wrote: On Wed, Oct 09, 2013 at 08:29:06AM -0700, Guenter Roeck wrote: On Wed, Oct 09, 2013 at 04:14:22PM +0200, Thierry Reding wrote: Hi all, I've uploaded today's linux-next tree to the master branch of the repository below:

linux-next: Tree for Oct 9

2012-10-08 Thread Stephen Rothwell
Hi all, Do not add stuff destined for v3.8 to your linux-next included branches until after v3.7-rc1 is released. Changes since 201201008: Conflicts are migrating as trees are merged by Linus. I have created today's

linux-next: Tree for Oct 9

2012-10-08 Thread Stephen Rothwell
Hi all, Do not add stuff destined for v3.8 to your linux-next included branches until after v3.7-rc1 is released. Changes since 201201008: Conflicts are migrating as trees are merged by Linus. I have created today's