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] [day] [month] [year] [list]

Message-ID: <CAP6Y9+_Q2p4E_ZHB3C_6OOUxtroTcvyzLYuY0JeNY3=5GWNgAg@mail.gmail.com>
Date:	Mon, 31 Aug 2015 17:35:33 -0700
From:	Chris Zankel <chris@...kel.net>
To:	Christoph Hellwig <hch@....de>,
	Andrew Morton <akpm@...ux-foundation.org>
Cc:	Max Filippov <jcmvbkbc@...il.com>,
	Guenter Roeck <linux@...ck-us.net>,
	"linux-xtensa@...ux-xtensa.org" <linux-xtensa@...ux-xtensa.org>,
	LKML <linux-kernel@...r.kernel.org>
Subject: Re: xtensa build failures in -next due to DMA API changes

Hi Andrew,

Linus has merged the Xtensa patches, so you should be ready to go.

Thanks,
-Chris

On Wed, Aug 26, 2015 at 10:41 AM, Christoph Hellwig <hch@....de> wrote:
> On Wed, Aug 26, 2015 at 10:53:25AM +0300, Max Filippov wrote:
>> Looks like I just need to remove now redundant function definitions from
>> xtensa/include/asm/dma-mapping.h. A patch that removes these
>> functions is attached, but I'm not sure where it should go. To the Andrew's
>> tree? Or should the xtensa tree merge Christoph's series and apply it on
>> top?
>
> This looks fine to me.  Thanks for converting xtensa to the generic
> DMA code!
--
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/