From: Sekhar Nori <nsekhar@ti.com>
To: Joel Fernandes <joelf@ti.com>, Vinod Koul <vinod.koul@intel.com>,
Jon Ringle <jon@ringle.org>
Cc: DMA Engine Mailing List <dmaengine@vger.kernel.org>,
"Ringle, Jonathan" <Jonathan.Ringle@gridpoint.com>,
Dan Williams <dan.j.williams@intel.com>,
"linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>,
Linux DaVinci Mailing List
<davinci-linux-open-source@linux.davincidsp.com>
Subject: Re: [PATCH] dma: edma: fix incorrect SG list handling
Date: Wed, 19 Mar 2014 15:50:20 +0530 [thread overview]
Message-ID: <53296F64.10308@ti.com> (raw)
In-Reply-To: <53291F72.9060504@ti.com>
On Wednesday 19 March 2014 10:09 AM, Sekhar Nori wrote:
> On Wednesday 19 March 2014 12:16 AM, Joel Fernandes wrote:
>> On 03/18/2014 10:28 AM, Vinod Koul wrote:
>>> where is this patch, somehow am not able to find in my inbox or archives...
>>>
>>
>> I found it archived here:
>> http://comments.gmane.org/gmane.linux.davinci/28569
>>
>> Patch doesn't breaking anything for > MAX_NR_SG list size on AM335x, so
>> it looks good.
>>
>> Acked-by: Joel Fernandes <joelf@ti.com>
>
> Joel, thanks for the ack.
>
> Vinod, Looks like the vger and Intel spam filters dropped the patch. I
> will try again.
Okay, I see see the patch in dmaengine list archives now and hopefully
it has reached Vinod too.
I think the issue last time around was that From: and Return-Path:
headers ended up having different addresses.
Thanks,
Sekhar
prev parent reply other threads:[~2014-03-19 10:20 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1395057448-22904-1-git-send-email-nsekhar@ti.com>
[not found] ` <alpine.DEB.2.02.1403170854570.9730@jringle-ubuntu>
[not found] ` <5326F2BF.6040702@ti.com>
[not found] ` <alpine.DEB.2.02.1403170913110.9730@jringle-ubuntu>
[not found] ` <20140318152840.GD1976@intel.com>
[not found] ` <20140318152840.GD1976-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
2014-03-18 18:46 ` [PATCH] dma: edma: fix incorrect SG list handling Joel Fernandes
2014-03-19 4:39 ` Sekhar Nori
2014-03-19 10:20 ` Sekhar Nori [this message]
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=53296F64.10308@ti.com \
--to=nsekhar@ti.com \
--cc=Jonathan.Ringle@gridpoint.com \
--cc=dan.j.williams@intel.com \
--cc=davinci-linux-open-source@linux.davincidsp.com \
--cc=dmaengine@vger.kernel.org \
--cc=joelf@ti.com \
--cc=jon@ringle.org \
--cc=linux-omap@vger.kernel.org \
--cc=vinod.koul@intel.com \
/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;
as well as URLs for NNTP newsgroup(s).