From: Laxman Dewangan <ldewangan-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
To: Mark Brown
<broonie-yzvPICuk2AATkU/dhu1WVueM+bqZidxxQQ4Iyu8u01E@public.gmane.org>
Cc: "grant.likely-s3s/WqlpOiPyB63q8FvJNQ@public.gmane.org"
<grant.likely-s3s/WqlpOiPyB63q8FvJNQ@public.gmane.org>,
"spi-devel-general-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org"
<spi-devel-general-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org>,
"swarren-3lzwWm7+Weoh9ZMKESR00Q@public.gmane.org"
<swarren-3lzwWm7+Weoh9ZMKESR00Q@public.gmane.org>,
"linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org"
<linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
"linux-tegra-u79uwXL29TY76Z2rM5mHXA@public.gmane.org"
<linux-tegra-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>
Subject: Re: [PATCH RESEND] spi: tegra: use dmaengine based dma driver
Date: Wed, 11 Jul 2012 15:44:26 +0530 [thread overview]
Message-ID: <4FFD5202.9080206@nvidia.com> (raw)
In-Reply-To: <20120711101527.GE3938-yzvPICuk2AATkU/dhu1WVueM+bqZidxxQQ4Iyu8u01E@public.gmane.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.
WARNING: multiple messages have this Message-ID (diff)
From: Laxman Dewangan <ldewangan@nvidia.com>
To: Mark Brown <broonie@opensource.wolfsonmicro.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 15:44:26 +0530 [thread overview]
Message-ID: <4FFD5202.9080206@nvidia.com> (raw)
In-Reply-To: <20120711101527.GE3938@opensource.wolfsonmicro.com>
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.
next prev parent reply other threads:[~2012-07-11 10:14 UTC|newest]
Thread overview: 11+ 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-10 13:38 ` Laxman Dewangan
2012-07-10 13:38 ` Laxman Dewangan
[not found] ` <1341927517-4584-1-git-send-email-ldewangan-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
2012-07-11 9:55 ` Mark Brown
2012-07-11 9:55 ` Mark Brown
[not found] ` <20120711095504.GD3938-yzvPICuk2AATkU/dhu1WVueM+bqZidxxQQ4Iyu8u01E@public.gmane.org>
2012-07-11 10:00 ` Laxman Dewangan
2012-07-11 10:00 ` Laxman Dewangan
[not found] ` <4FFD4ECA.8090304-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
2012-07-11 10:15 ` Mark Brown
2012-07-11 10:15 ` Mark Brown
[not found] ` <20120711101527.GE3938-yzvPICuk2AATkU/dhu1WVueM+bqZidxxQQ4Iyu8u01E@public.gmane.org>
2012-07-11 10:14 ` Laxman Dewangan [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=4FFD5202.9080206@nvidia.com \
--to=ldewangan-ddmlm1+adcrqt0dzr+alfa@public.gmane.org \
--cc=broonie-yzvPICuk2AATkU/dhu1WVueM+bqZidxxQQ4Iyu8u01E@public.gmane.org \
--cc=grant.likely-s3s/WqlpOiPyB63q8FvJNQ@public.gmane.org \
--cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-tegra-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=spi-devel-general-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
--cc=swarren-3lzwWm7+Weoh9ZMKESR00Q@public.gmane.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.