linux-next: Tree for Dec 14

2020-12-14 Thread Stephen Rothwell
Hi all, Changes since 20201211: The keys tree gained a build failure for which I applied a patch. The net-next tree gained a semantic conflict against the cifs tree. The drm tree gained a conflict against the crypto tree. The block tree gained a conflict and a semantic conflict against Linus'

Re: linux-next: Tree for Dec 14 (security/integrity/ima/)

2018-12-20 Thread James Morris
On Fri, 14 Dec 2018, Paul Gortmaker wrote: > >From 31081a8b46e84d64e2fbda8d0d82ba26d56cc468 Mon Sep 17 00:00:00 2001 > From: Paul Gortmaker > Date: Fri, 14 Dec 2018 16:48:07 -0500 > Subject: [PATCH] security: integrity: partial revert of make ima_main > explicitly non-modular > > In commit

Re: linux-next: Tree for Dec 14

2018-12-15 Thread Guenter Roeck
On Fri, Dec 14, 2018 at 06:18:26PM +1100, Stephen Rothwell wrote: > Hi all, > > Changes since 20181213: > > The dma-mapping tree gained a conflict against the kbuild tree. > > The rdma tree still had its build failure so I used a supplied patch. > > The net-next tree gained a conflict against

Re: linux-next: Tree for Dec 14 (security/integrity/ima/)

2018-12-14 Thread Paul Gortmaker
[Re: linux-next: Tree for Dec 14 (security/integrity/ima/)] On 14/12/2018 (Fri 15:26) Paul Gortmaker wrote: > [Re: linux-next: Tree for Dec 14 (security/integrity/ima/)] On 14/12/2018 > (Fri 14:19) Mimi Zohar wrote: > > > On Fri, 2018-12-14 at 08:25 -0800, Ran

Re: linux-next: Tree for Dec 14 (security/integrity/ima/)

2018-12-14 Thread Paul Gortmaker
[Re: linux-next: Tree for Dec 14 (security/integrity/ima/)] On 14/12/2018 (Fri 14:19) Mimi Zohar wrote: > [Cc'ing Paul Gortmaker] > > On Fri, 2018-12-14 at 08:25 -0800, Randy Dunlap wrote: > > On 12/13/18 11:18 PM, Stephen Rothwell wrote: > > > Hi all, > > &

Re: linux-next: Tree for Dec 14 (security/integrity/ima/)

2018-12-14 Thread Mimi Zohar
[Cc'ing Paul Gortmaker] On Fri, 2018-12-14 at 08:25 -0800, Randy Dunlap wrote: > On 12/13/18 11:18 PM, Stephen Rothwell wrote: > > Hi all, > > > > Changes since 20181213: > > > > on i386: > > CC security/integrity/ima/ima_main.o > ../security/integrity/ima/ima_main.c: In function

Re: linux-next: Tree for Dec 14 (security/integrity/ima/)

2018-12-14 Thread Randy Dunlap
On 12/13/18 11:18 PM, Stephen Rothwell wrote: > Hi all, > > Changes since 20181213: > on i386: CC security/integrity/ima/ima_main.o ../security/integrity/ima/ima_main.c: In function 'ima_load_data': ../security/integrity/ima/ima_main.c:535:3: error: implicit declaration of function

linux-next: Tree for Dec 14

2018-12-13 Thread Stephen Rothwell
Hi all, Changes since 20181213: The dma-mapping tree gained a conflict against the kbuild tree. The rdma tree still had its build failure so I used a supplied patch. The net-next tree gained a conflict against the bpf tree. The drm tree gained a conflict against the drm-fixes tree. The block

Re: linux-next: Tree for Dec 14 (usb/dwc3)

2017-12-15 Thread Vincent Pelletier
Hello, On Fri, 15 Dec 2017 10:17:17 +0200, Felipe Balbi wrote: > Randy Dunlap writes: > > On 12/13/2017 11:06 PM, Stephen Rothwell wrote: > >> Hi all, > >> > >> Changes since 20171213: > >> > > > > on i386: > > > > ERROR: "__tracepoint_dwc3_writel"

Re: linux-next: Tree for Dec 14 (usb/dwc3)

2017-12-15 Thread Vincent Pelletier
Hello, On Fri, 15 Dec 2017 10:17:17 +0200, Felipe Balbi wrote: > Randy Dunlap writes: > > On 12/13/2017 11:06 PM, Stephen Rothwell wrote: > >> Hi all, > >> > >> Changes since 20171213: > >> > > > > on i386: > > > > ERROR: "__tracepoint_dwc3_writel" [drivers/usb/dwc3/dwc3.ko] undefined! >

Re: linux-next: Tree for Dec 14 (usb/dwc3)

2017-12-15 Thread Felipe Balbi
Hi, Randy Dunlap writes: > On 12/13/2017 11:06 PM, Stephen Rothwell wrote: >> Hi all, >> >> Changes since 20171213: >> > > on i386: > > ERROR: "__tracepoint_dwc3_writel" [drivers/usb/dwc3/dwc3.ko] undefined! > ERROR: "__tracepoint_dwc3_readl" [drivers/usb/dwc3/dwc3.ko]

Re: linux-next: Tree for Dec 14 (usb/dwc3)

2017-12-15 Thread Felipe Balbi
Hi, Randy Dunlap writes: > On 12/13/2017 11:06 PM, Stephen Rothwell wrote: >> Hi all, >> >> Changes since 20171213: >> > > on i386: > > ERROR: "__tracepoint_dwc3_writel" [drivers/usb/dwc3/dwc3.ko] undefined! > ERROR: "__tracepoint_dwc3_readl" [drivers/usb/dwc3/dwc3.ko] undefined! > > > > I

Re: linux-next: Tree for Dec 14 (usb/dwc3)

2017-12-14 Thread Randy Dunlap
On 12/13/2017 11:06 PM, Stephen Rothwell wrote: > Hi all, > > Changes since 20171213: > on i386: ERROR: "__tracepoint_dwc3_writel" [drivers/usb/dwc3/dwc3.ko] undefined! ERROR: "__tracepoint_dwc3_readl" [drivers/usb/dwc3/dwc3.ko] undefined! I can send the randconfig file is you need it. --

Re: linux-next: Tree for Dec 14 (usb/dwc3)

2017-12-14 Thread Randy Dunlap
On 12/13/2017 11:06 PM, Stephen Rothwell wrote: > Hi all, > > Changes since 20171213: > on i386: ERROR: "__tracepoint_dwc3_writel" [drivers/usb/dwc3/dwc3.ko] undefined! ERROR: "__tracepoint_dwc3_readl" [drivers/usb/dwc3/dwc3.ko] undefined! I can send the randconfig file is you need it. --

linux-next: Tree for Dec 14

2017-12-13 Thread Stephen Rothwell
Hi all, Changes since 20171213: The staging.current tree gained a build failure for which I reverted a commit. The clk tree lost its build failures. The bpf-next tree lost its build failure. The drm tree gained a conflict against the drm-misc-fixes tree. Non-merge commits (relative to Linus'

linux-next: Tree for Dec 14

2017-12-13 Thread Stephen Rothwell
Hi all, Changes since 20171213: The staging.current tree gained a build failure for which I reverted a commit. The clk tree lost its build failures. The bpf-next tree lost its build failure. The drm tree gained a conflict against the drm-misc-fixes tree. Non-merge commits (relative to Linus'

Re: linux-next: Tree for Dec 14

2016-12-14 Thread Heiko Carstens
On Wed, Dec 14, 2016 at 11:25:49AM -0500, Paul Gortmaker wrote: > On Tue, Dec 13, 2016 at 11:22 PM, Stephen Rothwell > wrote: > > Hi all, > > > > Please do not add any material for v4.11 to your linux-next included > > branches until after v4.10-rc1 has been released. > >

Re: linux-next: Tree for Dec 14

2016-12-14 Thread Heiko Carstens
On Wed, Dec 14, 2016 at 11:25:49AM -0500, Paul Gortmaker wrote: > On Tue, Dec 13, 2016 at 11:22 PM, Stephen Rothwell > wrote: > > Hi all, > > > > Please do not add any material for v4.11 to your linux-next included > > branches until after v4.10-rc1 has been released. > > > > Changes since

Re: linux-next: Tree for Dec 14

2016-12-14 Thread Paul Gortmaker
On Tue, Dec 13, 2016 at 11:22 PM, Stephen Rothwell wrote: > Hi all, > > Please do not add any material for v4.11 to your linux-next included > branches until after v4.10-rc1 has been released. > > Changes since 20161213: > > The vfs-miklos tree gained a conflict against

Re: linux-next: Tree for Dec 14

2016-12-14 Thread Paul Gortmaker
On Tue, Dec 13, 2016 at 11:22 PM, Stephen Rothwell wrote: > Hi all, > > Please do not add any material for v4.11 to your linux-next included > branches until after v4.10-rc1 has been released. > > Changes since 20161213: > > The vfs-miklos tree gained a conflict against the ubifs tree. > > The

linux-next: Tree for Dec 14

2016-12-13 Thread Stephen Rothwell
Hi all, Please do not add any material for v4.11 to your linux-next included branches until after v4.10-rc1 has been released. Changes since 20161213: The vfs-miklos tree gained a conflict against the ubifs tree. The akpm-current tree gained a conflict against the jc_docs tree. Non-merge

linux-next: Tree for Dec 14

2016-12-13 Thread Stephen Rothwell
Hi all, Please do not add any material for v4.11 to your linux-next included branches until after v4.10-rc1 has been released. Changes since 20161213: The vfs-miklos tree gained a conflict against the ubifs tree. The akpm-current tree gained a conflict against the jc_docs tree. Non-merge

linux-next: Tree for Dec 14

2015-12-13 Thread Stephen Rothwell
Hi all, Changes since 20151211: The net-next tree gained a conflict against the pci tree. The drm-misc tree gained conflicts against the drm-intel and Linus' trees. The block tree gained a conflict against Linus' tree. Non-merge commits (relative to Linus' tree): 5241 5871 files changed,

linux-next: Tree for Dec 14

2015-12-13 Thread Stephen Rothwell
Hi all, Changes since 20151211: The net-next tree gained a conflict against the pci tree. The drm-misc tree gained conflicts against the drm-intel and Linus' trees. The block tree gained a conflict against Linus' tree. Non-merge commits (relative to Linus' tree): 5241 5871 files changed,

Re: linux-next: Tree for Dec 14 (net/can)

2012-12-14 Thread Marc Kleine-Budde
On 12/14/2012 08:19 PM, Randy Dunlap wrote: > On 12/13/12 23:42, Stephen Rothwell wrote: >> Hi all, >> >> Changes since 20121213: >> >> Lots of conflicts are migrating between trees. >> > > on X86_32: > > drivers/net/can/sja1000/sja1000_of_platform.c: In function > 'sja1000_ofp_probe': >

Re: linux-next: Tree for Dec 14 (net/can)

2012-12-14 Thread Marc Kleine-Budde
On 12/14/2012 08:19 PM, Randy Dunlap wrote: On 12/13/12 23:42, Stephen Rothwell wrote: Hi all, Changes since 20121213: Lots of conflicts are migrating between trees. on X86_32: drivers/net/can/sja1000/sja1000_of_platform.c: In function 'sja1000_ofp_probe':

linux-next: Tree for Dec 14

2012-12-13 Thread Stephen Rothwell
Hi all, Changes since 20121213: Lots of conflicts are migrating between trees. The powerpc tree lost its build failure. The xtensa tree gained a conflict against Linus' tree. The akpm tree lost lots of commits that turned up elsewhere and lost its build failure.

linux-next: Tree for Dec 14

2012-12-13 Thread Stephen Rothwell
Hi all, Changes since 20121213: Lots of conflicts are migrating between trees. The powerpc tree lost its build failure. The xtensa tree gained a conflict against Linus' tree. The akpm tree lost lots of commits that turned up elsewhere and lost its build failure.