Re: linux-next: Tree for Oct 5

2018-10-05 Thread Guenter Roeck
On Fri, Oct 05, 2018 at 04:39:43PM +1000, Stephen Rothwell wrote: > Hi all, > > Changes since 20181004: > > I added a supplied patch to the dma-mapping tree to fix overnight boot > problems. > > I added a supplied patch to the nfs tree to fix an overnight build > problem. > > The nfsd tree gain

linux-next: Tree for Oct 5

2018-10-04 Thread Stephen Rothwell
Hi all, Changes since 20181004: I added a supplied patch to the dma-mapping tree to fix overnight boot problems. I added a supplied patch to the nfs tree to fix an overnight build problem. The nfsd tree gained a build failure due to an interaction with the nfs tree for which I applied a merge f

linux-next: Tree for Oct 5

2016-10-04 Thread Stephen Rothwell
Hi all, There will be no linux-next release on Friday. Please do *not* add any v4.10 material to your linux-next included trees until v4.9-rc1 has been released i.e. the merge window closes. Changes since 20161004: Non-merge commits (relative to Linus' tree): 11868 8531 files changed, 482011 i

Re: linux-next: Tree for Oct 5 (nouveau)

2012-10-05 Thread Randy Dunlap
On 10/04/2012 09:54 PM, Stephen Rothwell wrote: > 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 201201004: > on x86_64, when CONFIG_AGP is not enabled: CC [M] drivers/gpu/drm/nouveau/nouveau_bo.o d

linux-next: Tree for Oct 5

2012-10-05 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 201201004: Conflicts are migrating as trees are merged by Linus. The net tree lost its build failure. The crypto tree lost its conflict. The drm tree lost its confli