linux-kernel - Re: [PATCH resend] arm: export dma_sync_sg_for

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]

Date:	Sun, 22 Jun 2008 15:46:44 +0100
From:	Russell King <rmk+lkml@....linux.org.uk>
To:	Stefan Richter <stefanr@...6.in-berlin.de>
Cc:	linux-kernel@...r.kernel.org,
	Andrew Morton <akpm@...ux-foundation.org>,
	Martin Michlmayr <tbm@...ius.com>
Subject: Re: [PATCH resend] arm: export dma_sync_sg_for_device (fix build failure)

On Sun, Jun 22, 2008 at 04:13:52PM +0200, Stefan Richter wrote:
> Date: 2006-06-18 03:49:35 +0200
> From: Stefan Richter <stefanr@...6.in-berlin.de>
> Subject: arm: add EXPORT_SYMBOL(dma_sync_sg_for_device)
> 
> as it is for example needed by drivers/ieee1394/dma.c
> 
> Signed-off-by: Stefan Richter <stefanr@...6.in-berlin.de>
> ---
>  arch/arm/common/dmabounce.c |    1 +
>  1 file changed, 1 insertion(+)
> 
> --- a/arch/arm/common/dmabounce.c
> +++ b/arch/arm/common/dmabounce.c
> @@ -651,6 +651,7 @@ EXPORT_SYMBOL(dma_unmap_sg);
>  EXPORT_SYMBOL(dma_sync_single_for_cpu);
>  EXPORT_SYMBOL(dma_sync_single_for_device);
>  EXPORT_SYMBOL(dma_sync_sg);
> +EXPORT_SYMBOL(dma_sync_sg_for_device);
>  EXPORT_SYMBOL(dmabounce_register_dev);
>  EXPORT_SYMBOL(dmabounce_unregister_dev);

I've just committed a better fix.  That dma_sync_sg export should be a
dma_sync_sg_for_cpu.  Thanks.

-- 
Russell King
 Linux kernel    2.6 ARM Linux   - http://www.arm.linux.org.uk/
 maintainer of:
--
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/