From: gregkh <gregkh@linuxfoundation.org>
To: Arnd Bergmann <arnd@arndb.de>
Cc: "Olof's autobuilder" <build@lixom.net>,
Olof Johansson <olof@lixom.net>,
Kernel Build Reports Mailman List
<kernel-build-reports@lists.linaro.org>,
stable <stable@vger.kernel.org>,
Jon Hunter <jonathanh@nvidia.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Lee Jones <lee.jones@linaro.org>
Subject: Re: stable-rc build: 0 warnings 7 failures (stable-rc/v3.18.90-13-g444eb56)
Date: Sat, 30 Dec 2017 16:29:23 +0100 [thread overview]
Message-ID: <20171230152923.GD26378@kroah.com> (raw)
In-Reply-To: <20171229091914.GG18441@kroah.com>
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@lixom.net> 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
prev parent reply other threads:[~2017-12-30 15:32 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <5a449f88.461f620a.1b6fd.4908@mx.google.com>
2017-12-28 8:39 ` stable-rc build: 0 warnings 7 failures (stable-rc/v3.18.90-13-g444eb56) Arnd Bergmann
2017-12-29 9:19 ` gregkh
2017-12-30 15:29 ` gregkh [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20171230152923.GD26378@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=arnd@arndb.de \
--cc=build@lixom.net \
--cc=jonathanh@nvidia.com \
--cc=kernel-build-reports@lists.linaro.org \
--cc=lee.jones@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=olof@lixom.net \
--cc=stable@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.