Re: linux-next: Tree for Oct 12 (drivers/staging/media/atomisp/)

2020-10-12 Thread Randy Dunlap
On 10/12/20 2:59 AM, Stephen Rothwell wrote: > Hi all, > > Changes since 20201009: > on x86_64: In file included from ../drivers/staging/media/atomisp//pci/ia_css_control.h:25:0, from ../drivers/staging/media/atomisp//pci/ia_css.h:28, from ../drivers/staging

linux-next: Tree for Oct 12

2020-10-12 Thread Stephen Rothwell
Hi all, Changes since 20201009: New tree: counters The arm64 tree gained a conflict against the asm-generic tree. The net-next tree gained a conflict against the net tree. The tip tree still had its build failure for which I applied a supplied patch. The irqchip tree gained a conflict a

linux-next: Tree for Oct 12

2018-10-12 Thread Stephen Rothwell
Hi all, Changes since 20181011: The net-next tree gained conflicts against the net tree. The tip tree gained conflicts against Linus' tree. The xarray tree gained a conflict against the nnvdimm-fixes tree. Non-merge commits (relative to Linus' tree): 9879 9305 files changed, 476445 insertions

linux-next: Tree for Oct 12

2016-10-11 Thread Stephen Rothwell
Hi all, 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 20161011: The akpm-current tree gained some build failures for which I applied 2 patches. Non-merge commits (relative to Linus' tree): 24

Re: linux-next: Tree for Oct 12

2015-10-12 Thread Sedat Dilek
On Mon, Oct 12, 2015 at 10:30 AM, Stephen Rothwell wrote: > Hi all, > > Changes since 20151009: > > My fixes tree is empty again. > > The qcom tree gained a conflict against the arm-soc tree. > > I used the h8300 tree from next-20150828 since the current tree has been > rebased onto linux-next ag

linux-next: Tree for Oct 12

2015-10-12 Thread Stephen Rothwell
Hi all, Changes since 20151009: My fixes tree is empty again. The qcom tree gained a conflict against the arm-soc tree. I used the h8300 tree from next-20150828 since the current tree has been rebased onto linux-next again :-( The battery tree still had its build failure so I used the version

linux-next: Tree for Oct 12

2012-10-12 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 201201011: Conflicts are migrating as trees are merged by Linus. Linus' tree lost its build failure. The l2-mtd tree gained a build failure so I used the version from