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>,
"# 4.4.x" <stable@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: stable-rc/linux-4.4.y build: 178 builds: 3 failed, 175 passed, 3 errors, 3 warnings (v4.4.105-33-g60c2da397c68)
Date: Tue, 12 Dec 2017 12:59:09 +0100 [thread overview]
Message-ID: <20171212115909.GB13411@kroah.com> (raw)
In-Reply-To: <CAK8P3a2qRbX09qH2MPSvdwTWQa0rO6cn8Qjw4x7TtevyRR5_9w@mail.gmail.com>
On Tue, Dec 12, 2017 at 11:14:36AM +0100, Arnd Bergmann wrote:
> On Tue, Dec 12, 2017 at 12:38 AM, kernelci.org bot <bot@kernelci.org> wrote:
> > Build Failures Detected:
> >
> >
> > Errors and Warnings Detected:
> >
> > arm64: gcc version 5.3.1 20160412 (Linaro GCC 5.3-2016.05)
> > defconfig 1 error 1 warning
> > arm: gcc version 5.3.1 20160412 (Linaro GCC 5.3-2016.05)
> > exynos_defconfig 1 error 1 warning
> > multi_v7_defconfig 1 error 1 warning
> > Errors summary:
> > 2 drivers/gpu/drm/exynos/exynos_drm_gem.c:254:3: error: implicit declaration of function 'DRM_WARN' [-Werror=implicit-function-declaration]
>
> Backporting commit 120a264f9c27 ("drm/exynos: gem: Drop NONCONTIG flag
> for buffers
> allocated without IOMMU") depends on commit
>
> 30b0da8d556e ("drm: extra printk() wrapper macros")
>
> which was merged into linux-4.9.
Now picked up, thanks.
greg k-h
prev parent reply other threads:[~2017-12-12 11:59 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <5a2f1707.c4141c0a.4b4a7.293b@mx.google.com>
2017-12-12 10:14 ` stable-rc/linux-4.4.y build: 178 builds: 3 failed, 175 passed, 3 errors, 3 warnings (v4.4.105-33-g60c2da397c68) Arnd Bergmann
2017-12-12 11:57 ` gregkh
2017-12-12 11: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=20171212115909.GB13411@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=arnd@arndb.de \
--cc=bot@kernelci.org \
--cc=kernel-build-reports@lists.linaro.org \
--cc=linux-kernel@vger.kernel.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox