linux-kernel - Re: xtensa build failures in -next due to DMA API changes

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

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20150825202439.GA25236@lst.de>
Date:	Tue, 25 Aug 2015 22:24:39 +0200
From:	Christoph Hellwig <hch@....de>
To:	Guenter Roeck <linux@...ck-us.net>
Cc:	Christoph Hellwig <hch@....de>, Chris Zankel <chris@...kel.net>,
	Max Filippov <jcmvbkbc@...il.com>,
	Andrew Morton <akpm@...ux-foundation.org>,
	linux-xtensa@...ux-xtensa.org, linux-kernel@...r.kernel.org
Subject: Re: xtensa build failures in -next due to DMA API changes

On Tue, Aug 25, 2015 at 01:21:40PM -0700, Guenter Roeck wrote:
> I also see
> 
> arch/xtensa/include/asm/dma-mapping.h:#include <asm-generic/dma-mapping-common.h>
> 
> It looks like there is a conflict with "xtensa: reimplement DMA API using common
> helpers" by Max Filippov, which added the include. This patch is in -next.

Oh.  That one clashes badly with my whole series, basically each
of my patches will need the same work done for the other architectures
applied to xtensa as well.

In terms of effort it might be a better idea to rebase the patch from
Max on top of the series, as it will become a lot simpler that way.
--
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/