From: Sergei Shtylyov <sshtylyov@mvista.com>
To: Sascha Hauer <s.hauer@pengutronix.de>
Cc: linux-arm-kernel@lists.infradead.org,
Dan Williams <dan.j.williams@intel.com>,
linux-kernel@vger.kernel.org
Subject: Re: dmaengine: i.MX dma fixes
Date: Mon, 31 Jan 2011 15:21:32 +0300 [thread overview]
Message-ID: <4D46A94C.7000700@ru.mvista.com> (raw)
In-Reply-To: <1296475248-29095-1-git-send-email-s.hauer@pengutronix.de>
Hello.
On 31-01-2011 15:00, Sascha Hauer wrote:
> The following contains fixes for the i.MX dma driver.
> Sascha
> The following changes since commit 1bae4ce27c9c90344f23c65ea6966c50ffeae2f5:
> Linux 2.6.38-rc2 (2011-01-21 19:01:34 -0800)
> are available in the git repository at:
> git://git.pengutronix.de/git/imx/linux-2.6 dmaengine-imxdma
> Sascha Hauer (4):
> dmaengine i.MX dma: set maximum segment size for our device
> dmaengine i.MX dma: check sg entries for valid addresses and lengths
> dmaengine i.MX DMA: do not initialize chan_id field
> dmaengine i.MX dma: initialize dma capabilities outside channel loop
> drivers/dma/imx-dma.c | 26 ++++++++++++++++++++++----
> 1 files changed, 22 insertions(+), 4 deletions(-)
Actually, would have made sense to combine the analogous changes to SDMA
and DMA drivers into the single patch...
WBR, Sergei
prev parent reply other threads:[~2011-01-31 12:22 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-31 12:00 dmaengine: i.MX dma fixes Sascha Hauer
2011-01-31 12:00 ` [PATCH 1/4] dmaengine i.MX dma: set maximum segment size for our device Sascha Hauer
2011-01-31 12:00 ` [PATCH 2/4] dmaengine i.MX dma: check sg entries for valid addresses and lengths Sascha Hauer
2011-01-31 12:00 ` [PATCH 3/4] dmaengine i.MX DMA: do not initialize chan_id field Sascha Hauer
2011-01-31 12:00 ` [PATCH 4/4] dmaengine i.MX dma: initialize dma capabilities outside channel loop Sascha Hauer
2011-01-31 12:21 ` Sergei Shtylyov [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=4D46A94C.7000700@ru.mvista.com \
--to=sshtylyov@mvista.com \
--cc=dan.j.williams@intel.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=s.hauer@pengutronix.de \
/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