linux-next: Tree for Nov 29

2018-11-28 Thread Stephen Rothwell
Hi all, Changes since 20181128: Non-merge commits (relative to Linus' tree): 5335 5517 files changed, 266627 insertions(+), 155239 deletions(-) I have created today's linux-next tree at

linux-next: Tree for Nov 29

2018-11-28 Thread Stephen Rothwell
Hi all, Changes since 20181128: Non-merge commits (relative to Linus' tree): 5335 5517 files changed, 266627 insertions(+), 155239 deletions(-) I have created today's linux-next tree at

linux-next: Tree for Nov 29

2017-11-28 Thread Stephen Rothwell
Hi all, Changes since 20171128: New trees: bpf, bpf-next Renamed tree: kvm-master to kvm-fixes Dropped tree: vfs (badly conflicting commit) The vfs tree gained conflicts against Linus' tree so I dropped it for today. The i2c tree lost its build failure. The etnaviv tree still had its

linux-next: Tree for Nov 29

2017-11-28 Thread Stephen Rothwell
Hi all, Changes since 20171128: New trees: bpf, bpf-next Renamed tree: kvm-master to kvm-fixes Dropped tree: vfs (badly conflicting commit) The vfs tree gained conflicts against Linus' tree so I dropped it for today. The i2c tree lost its build failure. The etnaviv tree still had its

linux-next: Tree for Nov 29

2016-11-28 Thread Stephen Rothwell
Hi all, Changes since 20161128: The net-next tree gained conflicts against the net tree. The crypto tree gained a build failure so I used the version from next-20161128. The akpm-current tree still had its build failure for which I added a supplied patch. Non-merge commits (relative to Linus'

linux-next: Tree for Nov 29

2016-11-28 Thread Stephen Rothwell
Hi all, Changes since 20161128: The net-next tree gained conflicts against the net tree. The crypto tree gained a build failure so I used the version from next-20161128. The akpm-current tree still had its build failure for which I added a supplied patch. Non-merge commits (relative to Linus'

Re: linux-next: Tree for Nov 29 (i915/intel_opregion)

2013-11-29 Thread Randy Dunlap
On 11/28/13 18:45, Stephen Rothwell wrote: > Hi all, > > Changes since 20131128: > on x86_64: CONFIG_ACPI is not enabled. CC drivers/gpu/drm/i915/intel_opregion.o In file included from drivers/gpu/drm/i915/intel_opregion.c:31:0: include/linux/acpi_io.h:7:45: error: unknown type name

Re: linux-next: Tree for Nov 29 (sfi)

2013-11-29 Thread Randy Dunlap
On 11/28/13 18:45, Stephen Rothwell wrote: > Hi all, > > Changes since 20131128: > on x86_64: when CONFIG_ACPI is not enabled: CC drivers/sfi/sfi_acpi.o drivers/sfi/sfi_acpi.c: In function 'sfi_acpi_parse_xsdt': drivers/sfi/sfi_acpi.c:105:12: error: dereferencing pointer to incomplete

Re: linux-next: Tree for Nov 29 (sfi)

2013-11-29 Thread Randy Dunlap
On 11/28/13 18:45, Stephen Rothwell wrote: Hi all, Changes since 20131128: on x86_64: when CONFIG_ACPI is not enabled: CC drivers/sfi/sfi_acpi.o drivers/sfi/sfi_acpi.c: In function 'sfi_acpi_parse_xsdt': drivers/sfi/sfi_acpi.c:105:12: error: dereferencing pointer to incomplete type

Re: linux-next: Tree for Nov 29 (i915/intel_opregion)

2013-11-29 Thread Randy Dunlap
On 11/28/13 18:45, Stephen Rothwell wrote: Hi all, Changes since 20131128: on x86_64: CONFIG_ACPI is not enabled. CC drivers/gpu/drm/i915/intel_opregion.o In file included from drivers/gpu/drm/i915/intel_opregion.c:31:0: include/linux/acpi_io.h:7:45: error: unknown type name

linux-next: Tree for Nov 29

2013-11-28 Thread Stephen Rothwell
Hi all, Changes since 20131128: The slave-dma tree gained conflicts against the imx-mxs tree. The sound-asoc tree gained a build failure so I used teh version from next-20131128. Non-merge commits (relative to Linus' tree): 1585 1774 files changed, 68549 insertions(+), 33718 deletions(-)

linux-next: Tree for Nov 29

2013-11-28 Thread Stephen Rothwell
Hi all, Changes since 20131128: The slave-dma tree gained conflicts against the imx-mxs tree. The sound-asoc tree gained a build failure so I used teh version from next-20131128. Non-merge commits (relative to Linus' tree): 1585 1774 files changed, 68549 insertions(+), 33718 deletions(-)

Re: linux-next: Tree for Nov 29 (netlabel)

2012-11-30 Thread Casey Schaufler
On 11/30/2012 8:55 AM, Randy Dunlap wrote: > On 11/30/2012 07:31 AM, Paul Moore wrote: > >> On Friday, November 30, 2012 10:19:16 AM Paul Moore wrote: >>> On Thursday, November 29, 2012 04:05:26 PM Randy Dunlap wrote: On 11/28/2012 10:40 PM, Stephen Rothwell wrote: > Hi all, > Changes

Re: linux-next: Tree for Nov 29 (netlabel)

2012-11-30 Thread Randy Dunlap
On 11/30/2012 07:31 AM, Paul Moore wrote: > On Friday, November 30, 2012 10:19:16 AM Paul Moore wrote: >> On Thursday, November 29, 2012 04:05:26 PM Randy Dunlap wrote: >>> On 11/28/2012 10:40 PM, Stephen Rothwell wrote: Hi all, >>> Changes since 20121128: >>> (on i386:) >> >> If I had

Re: linux-next: Tree for Nov 29 (netlabel)

2012-11-30 Thread Paul Moore
On Friday, November 30, 2012 10:19:16 AM Paul Moore wrote: > On Thursday, November 29, 2012 04:05:26 PM Randy Dunlap wrote: > > On 11/28/2012 10:40 PM, Stephen Rothwell wrote: > > > Hi all, > > > > > Changes since 20121128: > > (on i386:) > > If I had to guess it looks like CONFIG_NETLABEL needs

Re: linux-next: Tree for Nov 29 (netlabel)

2012-11-30 Thread Paul Moore
On Thursday, November 29, 2012 04:05:26 PM Randy Dunlap wrote: > On 11/28/2012 10:40 PM, Stephen Rothwell wrote: > > Hi all, > > > Changes since 20121128: > (on i386:) If I had to guess it looks like CONFIG_NETLABEL needs to be dependent on CONFIG_INET. While the net/ Kconfig only pulls in the

Re: linux-next: Tree for Nov 29 (netlabel)

2012-11-30 Thread Paul Moore
On Thursday, November 29, 2012 04:05:26 PM Randy Dunlap wrote: On 11/28/2012 10:40 PM, Stephen Rothwell wrote: Hi all, Changes since 20121128: (on i386:) If I had to guess it looks like CONFIG_NETLABEL needs to be dependent on CONFIG_INET. While the net/ Kconfig only pulls in the

Re: linux-next: Tree for Nov 29 (netlabel)

2012-11-30 Thread Paul Moore
On Friday, November 30, 2012 10:19:16 AM Paul Moore wrote: On Thursday, November 29, 2012 04:05:26 PM Randy Dunlap wrote: On 11/28/2012 10:40 PM, Stephen Rothwell wrote: Hi all, Changes since 20121128: (on i386:) If I had to guess it looks like CONFIG_NETLABEL needs to be

Re: linux-next: Tree for Nov 29 (netlabel)

2012-11-30 Thread Randy Dunlap
On 11/30/2012 07:31 AM, Paul Moore wrote: On Friday, November 30, 2012 10:19:16 AM Paul Moore wrote: On Thursday, November 29, 2012 04:05:26 PM Randy Dunlap wrote: On 11/28/2012 10:40 PM, Stephen Rothwell wrote: Hi all, Changes since 20121128: (on i386:) If I had to guess it looks like

Re: linux-next: Tree for Nov 29 (netlabel)

2012-11-30 Thread Casey Schaufler
On 11/30/2012 8:55 AM, Randy Dunlap wrote: On 11/30/2012 07:31 AM, Paul Moore wrote: On Friday, November 30, 2012 10:19:16 AM Paul Moore wrote: On Thursday, November 29, 2012 04:05:26 PM Randy Dunlap wrote: On 11/28/2012 10:40 PM, Stephen Rothwell wrote: Hi all, Changes since 20121128: (on