From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1757435Ab2CZLFM (ORCPT ); Mon, 26 Mar 2012 07:05:12 -0400 Received: from mga03.intel.com ([143.182.124.21]:56938 "EHLO mga03.intel.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1757307Ab2CZLFJ (ORCPT ); Mon, 26 Mar 2012 07:05:09 -0400 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="4.71,315,1320652800"; d="scan'208";a="123281524" Subject: Re: [PATCH linux-next] dmaengine: add context parameter fixups From: Vinod Koul To: Mark Brown Cc: Fabio Estevam , Alexandre Bounine , paul.gortmaker@windriver.com, dan.j.williams@intel.com, samuel@sortiz.org, lrg@ti.com, perex@perex.cz, tiwai@suse.de, linux-kernel@vger.kernel.org, linux-next@vger.kernel.org, netdev@vger.kernel.org, fabio.estevam@freescale.com, alsa-devel@alsa-project.org In-Reply-To: <20120326110149.GL3098@opensource.wolfsonmicro.com> References: <1332511242-30241-1-git-send-email-alexandre.bounine@idt.com> <1332740082.19804.15.camel@vkoul-udesk3> <20120326094200.GA3098@opensource.wolfsonmicro.com> <1332755670.19804.91.camel@vkoul-udesk3> <20120326103354.GD3098@opensource.wolfsonmicro.com> <1332758906.19804.97.camel@vkoul-udesk3> <20120326110149.GL3098@opensource.wolfsonmicro.com> Content-Type: text/plain; charset="UTF-8" Date: Mon, 26 Mar 2012 16:37:57 +0530 Message-ID: <1332760077.19804.98.camel@vkoul-udesk3> Mime-Version: 1.0 X-Mailer: Evolution 2.28.3 Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Mon, 2012-03-26 at 12:01 +0100, Mark Brown wrote: > On Mon, Mar 26, 2012 at 04:18:26PM +0530, Vinod Koul wrote: > > > But we don't want the clients to use this additional parameter or be > > exposed to it if not required. Every client is expected to use the > > dmaengine wrappers for prepare and not invoke .device_ callbacks. > > Are those wrappers present in what's gone to Linus' tree, and can > someone please send a patch to convert to using them? Yes that are already there :-) I will send sound specific update now -- ~Vinod