linux-kernel - Re: [PATCH] mlx4: replace the dma_sync_single_range_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] [thread-next>] [day] [month] [year] [list]

Date:	Fri, 19 Feb 2010 16:44:29 +0900
From:	FUJITA Tomonori <fujita.tomonori@....ntt.co.jp>
To:	davem@...emloft.net
Cc:	fujita.tomonori@....ntt.co.jp, netdev@...r.kernel.org,
	rolandd@...co.com, eli@...lanox.co.il, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] mlx4: replace the dma_sync_single_range_for_cpu/device
 API

On Thu, 11 Feb 2010 14:31:22 -0800
Roland Dreier <rdreier@...co.com> wrote:

>  > > There are only two users of the dma_sync_single_range_for_cpu/device
>  > > API in mainline (mlx4 and ssb). The
>  > > dma_sync_single_range_for_cpu/device API has never been documented and
>  > > the dma_sync_single_for_cpu/device API also support a partial sync.
>  > > 
>  > > This converts mlx4 to use the dma_sync_single_for_cpu/device API
>  > > (preparations for the removal of the dma_sync_single_range_for_cpu/device API).
>  > > 
>  > > Signed-off-by: FUJITA Tomonori <fujita.tomonori@....ntt.co.jp>
>  > 
>  > Acked-by: David S. Miller <davem@...emloft.net>
> 
> Dave, please go ahead and merge this -- this affects the mlx4 ethernet
> driver, so it's your area anyway.

Seems that net-next still doesn't have this. Can you please merge
this?

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