public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Laxman Dewangan <ldewangan@nvidia.com>
Cc: "grant.likely@secretlab.ca" <grant.likely@secretlab.ca>,
	"spi-devel-general@lists.sourceforge.net" 
	<spi-devel-general@lists.sourceforge.net>,
	"swarren@wwwdotorg.org" <swarren@wwwdotorg.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"linux-tegra@vger.kernel.org" <linux-tegra@vger.kernel.org>
Subject: Re: [PATCH RESEND] spi: tegra: use dmaengine based dma driver
Date: Wed, 11 Jul 2012 11:15:27 +0100	[thread overview]
Message-ID: <20120711101527.GE3938@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <4FFD4ECA.8090304@nvidia.com>

[-- Attachment #1: Type: text/plain, Size: 579 bytes --]

On Wed, Jul 11, 2012 at 03:30:42PM +0530, Laxman Dewangan wrote:
> On Wednesday 11 July 2012 03:25 PM, Mark Brown wrote:

> >Is this any different to the version of the patch that I already
> >applied?

> 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

> BTW, are you taking the same in regulator subsystem or created new
> for spi? I can verify from there.

I'm sorry, I can't parse this sentance at all.

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]

  reply	other threads:[~2012-07-11 10:15 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-07-10 13:38 [PATCH RESEND] spi: tegra: use dmaengine based dma driver Laxman Dewangan
2012-07-11  9:55 ` Mark Brown
2012-07-11 10:00   ` Laxman Dewangan
2012-07-11 10:15     ` Mark Brown [this message]
2012-07-11 10:14       ` Laxman Dewangan

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20120711101527.GE3938@opensource.wolfsonmicro.com \
    --to=broonie@opensource.wolfsonmicro.com \
    --cc=grant.likely@secretlab.ca \
    --cc=ldewangan@nvidia.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-tegra@vger.kernel.org \
    --cc=spi-devel-general@lists.sourceforge.net \
    --cc=swarren@wwwdotorg.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox