From: gregkh <gregkh@linuxfoundation.org>
To: Arnd Bergmann <arnd@arndb.de>
Cc: "kernelci.org bot" <bot@kernelci.org>,
Kernel Build Reports Mailman List
<kernel-build-reports@lists.linaro.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
ashwanth@codeaurora.org, "David S. Miller" <davem@davemloft.net>,
Aleksa Sarai <asarai@suse.de>
Subject: Re: next/master build: 208 builds: 2 failed, 206 passed, 2 errors, 147 warnings (next-20170613)
Date: Wed, 14 Jun 2017 11:59:58 +0200 [thread overview]
Message-ID: <20170614095958.GA12903@kroah.com> (raw)
In-Reply-To: <CAK8P3a1+=51AQ7R11SMWUynLaiVJ_9KciwwfAaXofN05TbUrUA@mail.gmail.com>
On Tue, Jun 13, 2017 at 01:59:40PM +0200, Arnd Bergmann wrote:
> On Tue, Jun 13, 2017 at 11:56 AM, kernelci.org bot <bot@kernelci.org> wrote:
> >
> > next/master build: 208 builds: 2 failed, 206 passed, 2 errors, 147 warnings (next-20170613)
> > Full Build Summary: https://kernelci.org/build/next/branch/master/kernel/next-20170613/
> > Tree: next
> > Branch: master
> > Git Describe: next-20170613
> > Git Commit: bc4c75f41a1ceb456d6a73c1cdbc5f0350200c16
> > Git URL: http://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git
> > Built: 4 unique architectures
> >
> > Build Failures Detected:
> >
> > arm: gcc version 5.3.1 20160412 (Linaro GCC 5.3-2016.05)
> > rpc_defconfig FAIL
> > Errors summary:
> > 1 arch/arm/mach-rpc/ecard.c:799:23: error: 'vendor_show' undeclared here (not in a function)
> > 1 arch/arm/mach-rpc/ecard.c:794:1: error: expected ',' or ';' before 'static'
>
> Caused by 71d1e5d71cec ("arm: ecard: use dev_groups and not dev_attrs
> for bus_type"), missing ';' after
>
> +static DEVICE_ATTR_RO(resource_show)
Should now be fixed, sorry for the noise.
greg k-h
prev parent reply other threads:[~2017-06-14 10:00 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <593fb6bf.8e471c0a.b6399.5a75@mx.google.com>
2017-06-13 11:59 ` Arnd Bergmann
2017-06-13 13:13 ` gregkh
2017-06-13 15:32 ` David Miller
2017-06-14 9:59 ` 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=20170614095958.GA12903@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=arnd@arndb.de \
--cc=asarai@suse.de \
--cc=ashwanth@codeaurora.org \
--cc=bot@kernelci.org \
--cc=davem@davemloft.net \
--cc=kernel-build-reports@lists.linaro.org \
--cc=linux-kernel@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Powered by JetHome