From: Vinod Koul <vinod.koul@intel.com>
To: Peter Ujfalusi <peter.ujfalusi@ti.com>
Cc: dan.j.williams@intel.com, dmaengine@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-omap@vger.kernel.org,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v2 0/2] dmaengine: edma/omap-dma: max_burst validity checking
Date: Thu, 12 Oct 2017 22:14:59 +0530 [thread overview]
Message-ID: <20171012164459.GS30097@localhost> (raw)
In-Reply-To: <20171003083538.11044-1-peter.ujfalusi@ti.com>
On Tue, Oct 03, 2017 at 11:35:36AM +0300, Peter Ujfalusi wrote:
> Hi,
>
> Changes since v1:
> - Fixed typo in commit message
> - Separated from the 'dmaengine: core/edma/omap-dma: maximum SG len reporting'
> series
>
> Both eDMA and sDMA have limit on the maximum burst size. The two patch
> implements protection against too big burst size for both driver.
I have applied these, but had to hand fix the patches. I guess you should
use gmail or someother server to send patches
--
~Vinod
WARNING: multiple messages have this Message-ID (diff)
From: vinod.koul@intel.com (Vinod Koul)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2 0/2] dmaengine: edma/omap-dma: max_burst validity checking
Date: Thu, 12 Oct 2017 22:14:59 +0530 [thread overview]
Message-ID: <20171012164459.GS30097@localhost> (raw)
In-Reply-To: <20171003083538.11044-1-peter.ujfalusi@ti.com>
On Tue, Oct 03, 2017 at 11:35:36AM +0300, Peter Ujfalusi wrote:
> Hi,
>
> Changes since v1:
> - Fixed typo in commit message
> - Separated from the 'dmaengine: core/edma/omap-dma: maximum SG len reporting'
> series
>
> Both eDMA and sDMA have limit on the maximum burst size. The two patch
> implements protection against too big burst size for both driver.
I have applied these, but had to hand fix the patches. I guess you should
use gmail or someother server to send patches
--
~Vinod
next prev parent reply other threads:[~2017-10-12 16:44 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-03 8:35 [PATCH v2 0/2] dmaengine: edma/omap-dma: max_burst validity checking Peter Ujfalusi
2017-10-03 8:35 ` Peter Ujfalusi
2017-10-03 8:35 ` Peter Ujfalusi
2017-10-03 8:35 ` [PATCH v2 1/2] dmaengine: edma: Implement protection for invalid max_burst Peter Ujfalusi
2017-10-03 8:35 ` Peter Ujfalusi
2017-10-03 8:35 ` Peter Ujfalusi
2017-10-03 8:35 ` [PATCH v2 2/2] dmaengine: omap-dma: " Peter Ujfalusi
2017-10-03 8:35 ` Peter Ujfalusi
2017-10-03 8:35 ` Peter Ujfalusi
2017-10-12 16:44 ` Vinod Koul [this message]
2017-10-12 16:44 ` [PATCH v2 0/2] dmaengine: edma/omap-dma: max_burst validity checking Vinod Koul
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=20171012164459.GS30097@localhost \
--to=vinod.koul@intel.com \
--cc=dan.j.williams@intel.com \
--cc=dmaengine@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=peter.ujfalusi@ti.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 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.