Re: stable-rc build: 0 warnings 7 failures (stable-rc/v3.18.90-13-g444eb56)

From: gregkh
Date: Sat Dec 30 2017 - 10:32:17 EST


On Fri, Dec 29, 2017 at 10:19:14AM +0100, gregkh wrote:
> On Thu, Dec 28, 2017 at 09:39:22AM +0100, Arnd Bergmann wrote:
> > On Thu, Dec 28, 2017 at 8:38 AM, Olof's autobuilder <build@xxxxxxxxx> wrote:
> > > Here are the build results from automated periodic testing.
> > >
> > > The tree being built was stable-rc, found at:
> > >
> > > URL: git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git
> > >
> > > Branch: linux-3.18.y
> > >
> > > Topmost commits:
> > > 444eb56 Linux 3.18.91-rc1
> > > d50e6c4 net: mvneta: clear interface link status on port disable
> > > 52e4bc8 powerpc/perf: Dereference BHRB entries safely
> > >
> > > Build logs (stderr only) can be found at the following link (experimental):
> > >
> > > http://arm-soc.lixom.net/buildlogs/stable-rc/v3.18.90-13-g444eb56/
> > >
> > >
> > > Runtime: 37m 53s
> > >
> > > Passed: 125
> > > Failed: 7
> > >
> > > Warnings: 0
> > >
> > > Section mismatches: 0
> > >
> > > -------------------------------------------------------------------------------
> > >
> > > Failed defconfigs:
> > > arm64.allmodconfig
> > > arm.allmodconfig
> > > arm.exynos_defconfig
> > > arm.multi_lpae_defconfig
> > > arm.multi_v7_defconfig
> > > arm.multi_v7_nosmp_defconfig
> > > arm.tegra_defconfig
> > >
> > > -------------------------------------------------------------------------------
> > >
> > > Errors:
> > >
> > > arm64.allmodconfig:
> > > /work/build/batch/drivers/mfd/cros_ec_spi.c:26:8: error: expected '=', ',', ';', 'asm' or '__attribute__' before '->' token
> > >
> > > arm.allmodconfig:
> > > /work/build/batch/drivers/mfd/cros_ec_spi.c:26:8: error: expected '=', ',', ';', 'asm' or '__attribute__' before '->' token
> >
> > This commit evidently got messed up during backporting:
> >
> > https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git/commit/?h=linux-3.18.y&id=bb97b859247c491356cf7bc1d187b323ba926b7a
>
> Ugh, something went really wrong there, thanks, I'll look into it on
> Monday.

Should now be fixed, thanks.

greg k-h