From: ezequiel.garcia@free-electrons.com (Ezequiel Garcia)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 0/3] dma: mv_xor: spinlock related improvements
Date: Fri, 27 Dec 2013 12:54:36 -0300 [thread overview]
Message-ID: <20131227155435.GC15734@localhost> (raw)
In-Reply-To: <1388144314-1581-1-git-send-email-thomas.petazzoni@free-electrons.com>
On Fri, Dec 27, 2013 at 12:38:31PM +0100, Thomas Petazzoni wrote:
> Vinod, Dan,
>
> Here are three patches that make improvements to the spinlock handling
> of the mv_xor driver. The first patch fixes a lock/release of the
> channel spinlock in mv_xor_status(), and the next two patches make
> followup code improvements/refactoring.
>
> Ezequiel, it would be good to have your review on these patches, since
> I know you've spent some time lately doing mv_xor stuff.
>
Spinlocks aren't the easiest thing to get right, and this driver is not
particularly simple. Anyway, to the best of my knowledge:
Reviewed-by: Ezequiel Garcia <ezequiel.garcia@free-electrons.com>
--
Ezequiel Garc?a, Free Electrons
Embedded Linux, Kernel and Android Engineering
http://free-electrons.com
next prev parent reply other threads:[~2013-12-27 15:54 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-27 11:38 [PATCH 0/3] dma: mv_xor: spinlock related improvements Thomas Petazzoni
2013-12-27 11:38 ` [PATCH 1/3] dma: mv_xor: take channel spinlock in mv_xor_status() Thomas Petazzoni
2013-12-30 9:55 ` Shevchenko, Andriy
2013-12-31 22:48 ` Dan Williams
2014-03-07 15:51 ` Ezequiel Garcia
2013-12-27 11:38 ` [PATCH 2/3] dma: mv_xor: use __mv_xor_slot_cleanup() in mv_xor_free_chan_resources() Thomas Petazzoni
2013-12-27 11:38 ` [PATCH 3/3] dma: mv_xor: rename __mv_xor_slot_cleanup() to mv_xor_slot_cleanup() Thomas Petazzoni
2013-12-27 15:54 ` Ezequiel Garcia [this message]
2013-12-27 17:48 ` [PATCH 0/3] dma: mv_xor: spinlock related improvements Jason Cooper
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=20131227155435.GC15734@localhost \
--to=ezequiel.garcia@free-electrons.com \
--cc=linux-arm-kernel@lists.infradead.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;
as well as URLs for NNTP newsgroup(s).