From: Mark Brown <broonie@kernel.org>
To: Lecopzer Chen <lecopzer.chen@mediatek.com>,
Mark-PK Tsai <Mark-PK.Tsai@mediatek.com>,
Andrew Morton <akpm@linux-foundation.org>,
Pavel Tatashin <pasha.tatashin@oracle.com>,
Oscar Salvador <osalvador@suse.de>,
Michal Hocko <mhocko@suse.com>,
Mike Rapoport <rppt@linux.ibm.com>
Cc: kernel-build-reports@lists.linaro.org, linux-mm@kvack.org,
linux-kernel@vger.kernel.org, linux-next@vger.kernel.org
Subject: Re: next/master build: 230 builds: 3 failed, 227 passed, 391 warnings (next-20190709)
Date: Tue, 9 Jul 2019 16:13:33 +0100 [thread overview]
Message-ID: <20190709151333.GD14859@sirena.co.uk> (raw)
In-Reply-To: <5d24a6be.1c69fb81.c03b6.0fc7@mx.google.com>
[-- Attachment #1: Type: text/plain, Size: 913 bytes --]
On Tue, Jul 09, 2019 at 07:37:50AM -0700, kernelci.org bot wrote:
Today's -next fails to build tinyconfig on arm64 and x86_64:
> arm64:
> tinyconfig: (clang-8) FAIL
> tinyconfig: (gcc-8) FAIL
>
> x86_64:
> tinyconfig: (gcc-8) FAIL
due to:
> tinyconfig (arm64, gcc-8) — FAIL, 0 errors, 0 warnings, 0 section mismatches
>
> Section mismatches:
> WARNING: vmlinux.o(.meminit.text+0x430): Section mismatch in reference from the function sparse_buffer_alloc() to the function .init.text:sparse_buffer_free()
> FATAL: modpost: Section mismatches detected.
(same error for all of them, the warning appears non-fatally in
other configs). This is caused by f13d13caa6ef2 (mm/sparse.c:
fix memory leak of sparsemap_buf in aliged memory) which adds a
reference from the __meminit annotated sparse_buffer_alloc() to
the newly added __init annotated sparse_buffer_free().
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next parent reply other threads:[~2019-07-09 15:13 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <5d24a6be.1c69fb81.c03b6.0fc7@mx.google.com>
2019-07-09 15:13 ` Mark Brown [this message]
2019-07-09 20:37 ` Andrew Morton
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=20190709151333.GD14859@sirena.co.uk \
--to=broonie@kernel.org \
--cc=Mark-PK.Tsai@mediatek.com \
--cc=akpm@linux-foundation.org \
--cc=kernel-build-reports@lists.linaro.org \
--cc=lecopzer.chen@mediatek.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux-next@vger.kernel.org \
--cc=mhocko@suse.com \
--cc=osalvador@suse.de \
--cc=pasha.tatashin@oracle.com \
--cc=rppt@linux.ibm.com \
/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