From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1757129Ab2GKKVM (ORCPT ); Wed, 11 Jul 2012 06:21:12 -0400 Received: from hqemgate03.nvidia.com ([216.228.121.140]:9330 "EHLO hqemgate03.nvidia.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751764Ab2GKKVJ (ORCPT ); Wed, 11 Jul 2012 06:21:09 -0400 X-PGP-Universal: processed; by hqnvupgp05.nvidia.com on Wed, 11 Jul 2012 03:20:55 -0700 Message-ID: <4FFD5202.9080206@nvidia.com> Date: Wed, 11 Jul 2012 15:44:26 +0530 From: Laxman Dewangan User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.13) Gecko/20101208 Thunderbird/3.1.7 MIME-Version: 1.0 To: Mark Brown CC: "grant.likely@secretlab.ca" , "spi-devel-general@lists.sourceforge.net" , "swarren@wwwdotorg.org" , "linux-kernel@vger.kernel.org" , "linux-tegra@vger.kernel.org" Subject: Re: [PATCH RESEND] spi: tegra: use dmaengine based dma driver References: <1341927517-4584-1-git-send-email-ldewangan@nvidia.com> <20120711095504.GD3938@opensource.wolfsonmicro.com> <4FFD4ECA.8090304@nvidia.com> <20120711101527.GE3938@opensource.wolfsonmicro.com> In-Reply-To: <20120711101527.GE3938@opensource.wolfsonmicro.com> Content-Type: text/plain; charset="ISO-8859-1"; format=flowed Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Wednesday 11 July 2012 03:45 PM, Mark Brown wrote: > * PGP Signed by an unknown key > > On Wed, Jul 11, 2012 at 03:30:42PM +0530, Laxman Dewangan wrote: >> On Wednesday 11 July 2012 03:25 PM, Mark Brown wrote: > >> I believe you have applied for the ASoC one. This is for spi one. > No, there's a dmaengine patch in my SPI branch too which I applied > yesterday. > > git://git.kernel.org/pub/scm/linux/kernel/git/broonie/misc.git spi-next > Looked at your misc/spi-next and you have already applied. This was just resend. Thanks for taking care. > > I'm sorry, I can't parse this sentance at all. > Just wanted to know that spi changes will be in regulator/for-next or some other tree. It is in misc/spi-next.