From: Mark Brown <broonie@kernel•org>
To: Sylwester Nawrocki <s.nawrocki@samsung•com>,
Javier Martinez Canillas <javier@osg•samsung.com>,
Marek Szyprowski <m.szyprowski@samsung•com>
Cc: kernel-build-reports@lists•linaro.org,
linaro-kernel@lists•linaro.org, linux-next@vger•kernel.org,
linux-arm-kernel@lists•infradead.org,
linux-samsung-soc@vger•kernel.org
Subject: Re: next-20160607 build: 2 failures 9 warnings (next-20160607)
Date: Tue, 7 Jun 2016 11:58:23 +0100 [thread overview]
Message-ID: <20160607105823.GT7510@sirena.org.uk> (raw)
In-Reply-To: <E1bABXS-0001YX-Cz@optimist>
[-- Attachment #1: Type: text/plain, Size: 465 bytes --]
On Tue, Jun 07, 2016 at 08:35:02AM +0100, Build bot for Mark Brown wrote:
Today's -next fails to build an arm64 allmodconfig due to:
> arm64-allmodconfig
> ../drivers/media/platform/s5p-mfc/s5p_mfc_iommu.h:19:27: fatal error: asm/dma-iommu.h: No such file or directory
introduced by 04f776734c4e (media: s5p-mfc: add iommu support) which
relies on a header which is only available on 32 bit ARM. I suspect the
driver should be using linux/dma-iommu.h instead.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 473 bytes --]
next prev parent reply other threads:[~2016-06-07 10:58 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-07 7:35 next-20160607 build: 2 failures 9 warnings (next-20160607) Build bot for Mark Brown
2016-06-07 10:58 ` Mark Brown [this message]
2016-06-07 11:32 ` [PATCH] media: s5p-mfc: fix compilation issue on archs other than ARM (32bit) Marek Szyprowski
2016-06-07 13:22 ` next-20160607 build: 2 failures 9 warnings (next-20160607) Sylwester Nawrocki
2016-06-07 13:33 ` Mauro Carvalho Chehab
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=20160607105823.GT7510@sirena.org.uk \
--to=broonie@kernel$(echo .)org \
--cc=javier@osg$(echo .)samsung.com \
--cc=kernel-build-reports@lists$(echo .)linaro.org \
--cc=linaro-kernel@lists$(echo .)linaro.org \
--cc=linux-arm-kernel@lists$(echo .)infradead.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=linux-samsung-soc@vger$(echo .)kernel.org \
--cc=m.szyprowski@samsung$(echo .)com \
--cc=s.nawrocki@samsung$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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