Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S932072AbVILPXC (ORCPT ); Mon, 12 Sep 2005 11:23:02 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S932077AbVILPXC (ORCPT ); Mon, 12 Sep 2005 11:23:02 -0400 Received: from ns1.suse.de ([195.135.220.2]:23486 "EHLO mx1.suse.de") by vger.kernel.org with ESMTP id S932072AbVILPXA (ORCPT ); Mon, 12 Sep 2005 11:23:00 -0400 From: Andi Kleen To: "John W. Linville" Subject: Re: [patch 2.6.13 6/6] x86_64: implement dma_sync_single_range_for_{cpu,device} Date: Mon, 12 Sep 2005 17:22:49 +0200 User-Agent: KMail/1.8 Cc: linux-kernel@vger.kernel.org, discuss@x86-64.org References: <09122005104851.31248@bilbo.tuxdriver.com> In-Reply-To: <09122005104851.31248@bilbo.tuxdriver.com> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200509121722.49649.ak@suse.de> Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 585 Lines: 13 On Monday 12 September 2005 16:48, John W. Linville wrote: > Implement dma_sync_single_range_for_{cpu,device} for x86_64. This > makes use of swiotlb_sync_single_range_for_{cpu,device}. I already have the simple patch that just used sync_single_range in my tree and it's scheduled to go to Linus ASAP. You can rebase on that later. -Andi - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/