lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
Open Source and information security mailing list archives
| ||
|
Date: Mon, 2 Nov 2015 09:15:07 +0900 From: Magnus Damm <magnus.damm@...il.com> To: Joerg Roedel <joro@...tes.org> Cc: Stephen Rothwell <sfr@...b.auug.org.au>, linux-next@...r.kernel.org, linux-kernel <linux-kernel@...r.kernel.org>, Magnus Damm <damm+renesas@...nsource.se> Subject: Re: linux-next: build failure after merge of the iommu tree Hi Joerg, everyone, On Mon, Nov 2, 2015 at 12:14 AM, Joerg Roedel <joro@...tes.org> wrote: > Hi Stephen, > > On Sun, Nov 01, 2015 at 10:42:52PM +1100, Stephen Rothwell wrote: >> After merging the iommu tree, today's linux-next build (x86_64 >> allmodconfig) failed like this: >> >> drivers/iommu/ipmmu-vmsa.c:24:27: fatal error: asm/dma-iommu.h: No such file or directory >> >> Caused by commit >> >> bad78b13e305 ("iommu/ipmmu-vmsa: Drop LPAE Kconfig dependency") >> >> Only arm has the include file ... >> >> I have used the iommu tree from next-20151022 for today. > > Thanks, I reverted the broken commit and will push out an updated tree > soon. Thanks for your help and my apologies for the breakage. I did not expect this patch to enable build on non-ARM platforms but I can now understand that the LPAE Kconfig bits may have been the last bit stopping other architectures to build this driver. I'm currently poking around with this driver on 32/64-bit ARM and getting rid of those includes from asm/ is for sure on my TODO list. / magnus -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists