linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: mchehab@osg.samsung.com (Mauro Carvalho Chehab)
To: linux-arm-kernel@lists.infradead.org
Subject: next-20160607 build: 2 failures 9 warnings (next-20160607)
Date: Tue, 7 Jun 2016 10:33:09 -0300	[thread overview]
Message-ID: <20160607103309.0b9a48fc@recife.lan> (raw)
In-Reply-To: <5756CAB2.5030701@samsung.com>

Em Tue, 07 Jun 2016 15:22:58 +0200
Sylwester Nawrocki <s.nawrocki@samsung.com> escreveu:

> 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)"

Sure. Applied, thanks!

Mauro

      reply	other threads:[~2016-06-07 13:33 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <E1bABXS-0001YX-Cz@optimist>
2016-06-07 10:58 ` next-20160607 build: 2 failures 9 warnings (next-20160607) 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   ` next-20160607 build: 2 failures 9 warnings (next-20160607) Sylwester Nawrocki
2016-06-07 13:33     ` Mauro Carvalho Chehab [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=20160607103309.0b9a48fc@recife.lan \
    --to=mchehab@osg.samsung.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    /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).