From: Sylwester Nawrocki <s.nawrocki@samsung.com>
To: Mauro Carvalho Chehab <mchehab@osg.samsung.com>
Cc: Mark Brown <broonie@kernel.org>,
Javier Martinez Canillas <javier@osg.samsung.com>,
Marek Szyprowski <m.szyprowski@samsung.com>,
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, 07 Jun 2016 15:22:58 +0200 [thread overview]
Message-ID: <5756CAB2.5030701@samsung.com> (raw)
In-Reply-To: <20160607105823.GT7510@sirena.org.uk>
On 06/07/2016 12:58 PM, Mark Brown wrote:
> 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.
Since the mfc topic branch got already pulled to the samsung-soc tree,
as discussed in other thread [1], there is a build break in -next.
There is a patch to fix this issue and to include it in next, as we
agreed on irc, could you please pull this branch into your "for-next"
tree:
git://linuxtv.org/snawrocki/samsung.git for-v4.8/media/exynos-mfc
and then apply that patch [2] ?
"media: s5p-mfc: fix compilation issue on archs other than ARM (32bit)"
--
Thanks,
Sylwester
[1] https://patchwork.linuxtv.org/patch/34495
[2] https://patchwork.linuxtv.org/patch/34515
next prev parent reply other threads:[~2016-06-07 13:22 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
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 ` Sylwester Nawrocki [this message]
2016-06-07 13:33 ` next-20160607 build: 2 failures 9 warnings (next-20160607) 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=5756CAB2.5030701@samsung.com \
--to=s.nawrocki@samsung.com \
--cc=broonie@kernel.org \
--cc=javier@osg.samsung.com \
--cc=kernel-build-reports@lists.linaro.org \
--cc=linaro-kernel@lists.linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-next@vger.kernel.org \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=m.szyprowski@samsung.com \
--cc=mchehab@osg.samsung.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;
as well as URLs for NNTP newsgroup(s).