Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1755716AbYFZWd3 (ORCPT ); Thu, 26 Jun 2008 18:33:29 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1752537AbYFZWdT (ORCPT ); Thu, 26 Jun 2008 18:33:19 -0400 Received: from yw-out-2324.google.com ([74.125.46.30]:24842 "EHLO yw-out-2324.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752491AbYFZWdS (ORCPT ); Thu, 26 Jun 2008 18:33:18 -0400 DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:sender:to:subject:cc:in-reply-to:mime-version :content-type:content-transfer-encoding:content-disposition :references:x-google-sender-auth; b=CJqiZ30Y664GN00wcF7FcifPVYH1WyxBORcdTLTHgFg35zuYhhxA/un5mfAYUZ8KV8 um6U55Pz/eOWO516350v/fVC8JqY9LmDLZtaC8kwqJCdUAHwTpimLptic+YByYrAIJ4B bZWlahA/jxfYhY8/fDZjAiWmyezgAQcvUbsvo= Message-ID: Date: Thu, 26 Jun 2008 15:33:16 -0700 From: "Dan Williams" To: "Nicolas Pitre" Subject: Re: [PATCH/RFC] DMA engine driver for Marvell XOR engine Cc: "Maciej Sosnowski" , "Saeed Bishara" , "Lennert Buytenhek" , "Russell King" , lkml , "Haavard Skinnemoen" In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: X-Google-Sender-Auth: 356d1ab956d86a54 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1062 Lines: 25 On Mon, Jun 23, 2008 at 9:46 AM, Nicolas Pitre wrote: > Here is a driver for the DMA/XOR engine found on many ARM SoCs from > Marvell, such as Orion and newly supported Kirkwood. Could interested > people (notably Maciej Sosnowski and Dan Williams who are listed as > maintainers for the DMA generic offload subsystem) review this patch, > and ultimately provide their ACK, so we could push this driver along > with additional ARM patches that depend on this one through the ARM git > tree. > Hi Nicolas, With Haavard's recently posted changes there is more activity in the dmaengine/async_tx space with implications to mv_xor. What difficulties arise if I carry mv_xor through async_tx.git instead of letting it go though arm.git, i.e. what patches do you have that depend on mv_xor? Thanks, Dan -- 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/