linux-kernel - Re: [patch] More defines for dma-mapping-broken.h

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: <45CF3B0F.9080406@garzik.org>
Date:	Sun, 11 Feb 2007 10:49:35 -0500
From:	Jeff Garzik <jeff@...zik.org>
To:	Heiko Carstens <heiko.carstens@...ibm.com>
CC:	Andrew Morton <akpm@...ux-foundation.org>,
	Linus Torvalds <torvalds@...ux-foundation.org>,
	Martin Schwidefsky <schwidefsky@...ibm.com>,
	Tejun Heo <htejun@...il.com>, linux-kernel@...r.kernel.org,
	linux-s390@...r.kernel.org
Subject: Re: [patch] More defines for dma-mapping-broken.h

Heiko Carstens wrote:
> From: Heiko Carstens <heiko.carstens@...ibm.com>
> 
> 9ac7849e35f705830f7b016ff272b0ff1f7ff759 causes this on s390.
> Since we don't support DMA extend dma-mapping-broken.h a bit.
> 
> drivers/base/dma-mapping.c: In function `dmam_noncoherent_release':
> drivers/base/dma-mapping.c:32:
> 	warning: implicit declaration of function `dma_free_noncoherent'
> drivers/base/dma-mapping.c: In function `dmam_alloc_noncoherent':
> drivers/base/dma-mapping.c:129:
> 	warning: implicit declaration of function `dma_alloc_noncoherent'
> drivers/base/dma-mapping.c:129:
> 	warning: assignment makes pointer from integer without a cast
> 
> Cc: Tejun Heo <htejun@...il.com>
> Cc: Jeff Garzik <jeff@...zik.org>
> Cc: Martin Schwidefsky <schwidefsky@...ibm.com>
> Signed-off-by: Heiko Carstens <heiko.carstens@...ibm.com>
> ---
>  include/asm-generic/dma-mapping-broken.h |    4 +++-
>  1 files changed, 3 insertions(+), 1 deletion(-)

ACK


-
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/