From: Mark Brown <broonie@kernel.org>
To: Oscar Salvador <osalvador@suse.de>,
Naoya Horiguchi <naoya.horiguchi@nec.com>,
Andrew Morton <akpm@linux-foundation.org>,
Stephen Rothwell <sfr@canb.auug.org.au>
Cc: linux-next@vger.kernel.org, linux-arm-kernel@lists.infradead.org
Subject: Re: next/master build: 147 builds: 21 failed, 126 passed, 102 errors, 149 warnings (next-20200626)
Date: Fri, 26 Jun 2020 17:08:57 +0100 [thread overview]
Message-ID: <20200626160857.GH5289@sirena.org.uk> (raw)
In-Reply-To: <5ef606ee.1c69fb81.1563a.0d3c@mx.google.com>
[-- Attachment #1: Type: text/plain, Size: 1133 bytes --]
On Fri, Jun 26, 2020 at 07:32:14AM -0700, kernelci.org bot wrote:
Today's -next fails to build on arm64 in a number of configurations:
> arm64:
> defconfig: (clang-10) FAIL
> defconfig: (clang-9) FAIL
> defconfig: (gcc-8) FAIL
> defconfig+CONFIG_CPU_BIG_ENDIAN=y: (gcc-8) FAIL
> defconfig+CONFIG_RANDOMIZE_BASE=y: (gcc-8) FAIL
> defconfig+kselftest: (gcc-8) FAIL
Due to:
> defconfig (arm64, clang-9) — FAIL, 3 errors, 0 warnings, 0 section mismatches
>
> Errors:
> mm/memory-failure.c:1827:3: error: implicit declaration of function 'page_handle_poison' [-Werror,-Wimplicit-function-declaration]
> mm/memory-failure.c:1837:9: error: implicit declaration of function 'page_handle_poison' [-Werror,-Wimplicit-function-declaration]
> mm/memory-failure.c:1870:7: error: implicit declaration of function 'page_handle_poison' [-Werror,-Wimplicit-function-declaration]
which looks like it was introduced by baed01e5fe3096f29e (mm,hwpoison:
rework soft offline for free pages), reverting that (and some of the
subsequent commits in the same series) fixes the build for me.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
prev parent reply other threads:[~2020-06-26 16:09 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-26 14:32 next/master build: 147 builds: 21 failed, 126 passed, 102 errors, 149 warnings (next-20200626) kernelci.org bot
2020-06-26 16:08 ` Mark Brown [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=20200626160857.GH5289@sirena.org.uk \
--to=broonie@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-next@vger.kernel.org \
--cc=naoya.horiguchi@nec.com \
--cc=osalvador@suse.de \
--cc=sfr@canb.auug.org.au \
/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;
as well as URLs for NNTP newsgroup(s).