linux-next: Tree for Apr 10

2019-04-10 Thread Stephen Rothwell
Hi all, Changes since 20190409: The printk tree gained conflicts against Linus' tree. The drm tree still had its build failure for which I disabled a driver. The drm-misc tree still had its build failure for which I marked a driver as BROKEN. The scsi tree inherited a build failure form the

linux-next: Tree for Apr 10

2018-04-09 Thread Stephen Rothwell
Hi all, Please do not add any v4.18 destined stuff to your linux-next included trees until after v4.17-rc1 has been released. Changes since 20180409: The parisc-hd tree still had its build failure for which I applied a patch. The nvdimm tree lost its build failure. Non-merge commits (relative

linux-next: Tree for Apr 10

2018-04-09 Thread Stephen Rothwell
Hi all, Please do not add any v4.18 destined stuff to your linux-next included trees until after v4.17-rc1 has been released. Changes since 20180409: The parisc-hd tree still had its build failure for which I applied a patch. The nvdimm tree lost its build failure. Non-merge commits (relative

linux-next: Tree for Apr 10

2017-04-10 Thread Stephen Rothwell
Hi all, Changes since 20170407: The md tree gained conflicts against the block tree. The mfd tree still had its build failure for which I reverted a commit. The clockevents tree gained a conflict against the arm-soc tree. The kvm-arm tree gained conflicts against the kvm and Linus' trees.

linux-next: Tree for Apr 10

2017-04-10 Thread Stephen Rothwell
Hi all, Changes since 20170407: The md tree gained conflicts against the block tree. The mfd tree still had its build failure for which I reverted a commit. The clockevents tree gained a conflict against the arm-soc tree. The kvm-arm tree gained conflicts against the kvm and Linus' trees.

Re: linux-next: Tree for Apr 10 (media/i2c/adp1653)

2015-04-10 Thread Sakari Ailus
Hi Randy and others, On Fri, Apr 10, 2015 at 10:25:23AM -0700, Randy Dunlap wrote: ... > > ../drivers/media/i2c/adp1653.c:433:6: warning: unused variable 'gpio' > > [-Wunused-variable] > > int gpio; A preliminary patch for adp1653 DT support was accidentally merged to media-tree. It's now

Re: linux-next: Tree for Apr 10 (media/i2c/adp1653)

2015-04-10 Thread Sakari Ailus
Hi Randy and others, On Fri, Apr 10, 2015 at 10:25:23AM -0700, Randy Dunlap wrote: ... ../drivers/media/i2c/adp1653.c:433:6: warning: unused variable 'gpio' [-Wunused-variable] int gpio; A preliminary patch for adp1653 DT support was accidentally merged to media-tree. It's now reverted

linux-next: Tree for Apr 10

2014-04-09 Thread Stephen Rothwell
Hi all, Please do not add material intended for v3.16 to your linux-next included branches until after v3.15-rc1 is released. This tree still fails (more than usual) the powerpc allyesconfig build. Changes since 20140409: Dropped trees: akpm-current, akpm (too complex conflicts) The arm tree

linux-next: Tree for Apr 10

2014-04-09 Thread Stephen Rothwell
Hi all, Please do not add material intended for v3.16 to your linux-next included branches until after v3.15-rc1 is released. This tree still fails (more than usual) the powerpc allyesconfig build. Changes since 20140409: Dropped trees: akpm-current, akpm (too complex conflicts) The arm tree

Re: linux-next: Tree for Apr 10 (media and OF)

2013-04-10 Thread Sylwester Nawrocki
On 04/10/2013 11:36 PM, Randy Dunlap wrote: On 04/10/13 01:48, Stephen Rothwell wrote: Hi all, Changes since 20130409: on i386: ERROR: "of_get_next_parent" [drivers/media/v4l2-core/videodev.ko] undefined! 'of_get_next_parent()' should be exported for use by modules...? Yes, there was

Re: linux-next: Tree for Apr 10 (meda and OF)

2013-04-10 Thread Randy Dunlap
On 04/10/13 01:48, Stephen Rothwell wrote: > Hi all, > > Changes since 20130409: > on i386: ERROR: "of_get_next_parent" [drivers/media/v4l2-core/videodev.ko] undefined! 'of_get_next_parent()' should be exported for use by modules...? -- ~Randy -- To unsubscribe from this list: send the

Re: linux-next: Tree for Apr 10

2013-04-10 Thread Sedat Dilek
On Wed, Apr 10, 2013 at 10:48 AM, Stephen Rothwell wrote: > Hi all, > > Changes since 20130409: > > The vfs tree lost its build failure. > Beyond build-failures in vfs-next [0] and [1], it was not bootable (see [2] till [4])! This is now all fixed, thanks to all involved people! $ cat

Re: linux-next: Tree for Apr 10

2013-04-10 Thread Sedat Dilek
On Wed, Apr 10, 2013 at 10:48 AM, Stephen Rothwell s...@canb.auug.org.au wrote: Hi all, Changes since 20130409: The vfs tree lost its build failure. Beyond build-failures in vfs-next [0] and [1], it was not bootable (see [2] till [4])! This is now all fixed, thanks to all involved people!

Re: linux-next: Tree for Apr 10 (meda and OF)

2013-04-10 Thread Randy Dunlap
On 04/10/13 01:48, Stephen Rothwell wrote: Hi all, Changes since 20130409: on i386: ERROR: of_get_next_parent [drivers/media/v4l2-core/videodev.ko] undefined! 'of_get_next_parent()' should be exported for use by modules...? -- ~Randy -- To unsubscribe from this list: send the line

Re: linux-next: Tree for Apr 10 (media and OF)

2013-04-10 Thread Sylwester Nawrocki
On 04/10/2013 11:36 PM, Randy Dunlap wrote: On 04/10/13 01:48, Stephen Rothwell wrote: Hi all, Changes since 20130409: on i386: ERROR: of_get_next_parent [drivers/media/v4l2-core/videodev.ko] undefined! 'of_get_next_parent()' should be exported for use by modules...? Yes, there was