From: Mark Brown <broonie@kernel.org>
To: Christoph Hellwig <hch@lst.de>, Russell King <linux@armlinux.org.uk>
Cc: kernel-build-reports@lists.linaro.org,
linux-next@vger.kernel.org, linux-arm-kernel@lists.infradead.org
Subject: Re: next/pending-fixes build: 222 builds: 3 failed, 219 passed, 3 errors, 425 warnings (v5.3-rc4-185-g260510fdbaa7)
Date: Tue, 13 Aug 2019 13:37:40 +0100 [thread overview]
Message-ID: <20190813123740.GD5093@sirena.co.uk> (raw)
In-Reply-To: <5d52a9c3.1c69fb81.69154.3085@mx.google.com>
[-- Attachment #1: Type: text/plain, Size: 998 bytes --]
On Tue, Aug 13, 2019 at 05:14:59AM -0700, kernelci.org bot wrote:
For the past few days -next has been failing to build configurations
with LPAE enabled:
> arm:
> axm55xx_defconfig: (gcc-8) FAIL
> keystone_defconfig: (gcc-8) FAIL
> multi_v7_defconfig+CONFIG_EFI=y+CONFIG_ARM_LPAE=y: (gcc-8) FAIL
due to errors related to dma_atomic_pool_init()
> Errors summary:
>
> 1 dma-mapping.c:(.init.text+0x18): undefined reference to `dma_atomic_pool_init'
> 1 /home/buildslave/workspace/workspace/kernel-build@8/linux/build/../arch/arm/mm/dma-mapping.c:2427: undefined reference to `dma_atomic_pool_init'
> 1 /home/buildslave/workspace/workspace/kernel-build@6/linux/build/../arch/arm/mm/dma-mapping.c:2427: undefined reference to `dma_atomic_pool_init'
caused by 896089d598c1d46 (arm: initialize the dma-remap atomic pool for
LPAE configs). Nothing ensures that DMA_DIRECT_REMAP is selected in
such configurations so that function is not built.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next parent reply other threads:[~2019-08-13 12:37 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <5d52a9c3.1c69fb81.69154.3085@mx.google.com>
2019-08-13 12:37 ` Mark Brown [this message]
2019-08-13 13:08 ` next/pending-fixes build: 222 builds: 3 failed, 219 passed, 3 errors, 425 warnings (v5.3-rc4-185-g260510fdbaa7) Christoph Hellwig
2019-08-13 12:14 kernelci.org bot
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=20190813123740.GD5093@sirena.co.uk \
--to=broonie@kernel.org \
--cc=hch@lst.de \
--cc=kernel-build-reports@lists.linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-next@vger.kernel.org \
--cc=linux@armlinux.org.uk \
/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).