From: Guennadi Liakhovetski <g.liakhovetski@gmx.de>
To: linux-kernel@vger.kernel.org
Cc: Dan Williams <dan.j.williams@intel.com>, linux-sh@vger.kernel.org
Subject: [PATCH 0/3 v2] sh: fix dma driver
Date: Thu, 10 Dec 2009 18:35:01 +0100 (CET) [thread overview]
Message-ID: <Pine.LNX.4.64.0912101826010.4487@axis700.grange> (raw)
Further testing with preempt enabled revealed more problems with
insufficient locking and improper descriptor state management. Therefore
I'm resubmitting the
sh: fix DMA driver's descriptor chaining and cookie assignment
patch. At the same time I swapped it with stylistic changes, to put the
complex stuff in the end. Also added a minor patch fixing comment in
dmaengine.h. Patches
sh: DMA driver has to specify its alignment requirements
dmaengine: fix dmatest to verify minimum transfer length and test buffer size
sh: dmaengine support for sh7724
are not changed, so, not resubmitted
Thanks
Guennadi
---
Guennadi Liakhovetski, Ph.D.
Freelance Open-Source Software Developer
http://www.open-technology.de/
next reply other threads:[~2009-12-10 17:34 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-10 17:35 Guennadi Liakhovetski [this message]
2009-12-10 17:35 ` [PATCH 1/3 v2] sh: stylistic improvements for the DMA driver Guennadi Liakhovetski
2009-12-10 17:35 ` [PATCH 2/3 v2] sh: fix DMA driver's descriptor chaining and cookie assignment Guennadi Liakhovetski
2009-12-11 8:02 ` Paul Mundt
2009-12-12 2:15 ` Nobuhiro Iwamatsu
2009-12-17 3:09 ` Nobuhiro Iwamatsu
2009-12-17 7:40 ` Guennadi Liakhovetski
2009-12-17 8:33 ` Nobuhiro Iwamatsu
2009-12-17 8:43 ` Guennadi Liakhovetski
2009-12-17 17:50 ` Dan Williams
2009-12-10 17:35 ` [PATCH 3/3] dmaengine: clarify the meaning of the DMA_CTRL_ACK flag Guennadi Liakhovetski
2009-12-12 4:58 ` [PATCH 0/3 v2] sh: fix dma driver Dan Williams
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=Pine.LNX.4.64.0912101826010.4487@axis700.grange \
--to=g.liakhovetski@gmx.de \
--cc=dan.j.williams@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sh@vger.kernel.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
all inboxes | Powered by JetHome®