From: Chris Ball <cjb@laptop.org>
To: Guennadi Liakhovetski <g.liakhovetski@gmx.de>
Cc: linux-mmc@vger.kernel.org, linux-sh@vger.kernel.org,
Magnus Damm <damm@opensource.se>,
"Rafael J. Wysocki" <rjw@sisk.pl>,
Ian Molton <ian@mnementh.co.uk>,
Simon Horman <horms@verge.net.au>
Subject: Re: [PATCH 0/2] mmc: tmio: two bug-fixes
Date: Thu, 14 Jul 2011 15:27:03 -0400 [thread overview]
Message-ID: <m2pqlcslx4.fsf@bob.laptop.org> (raw)
In-Reply-To: <Pine.LNX.4.64.1107141828470.10688@axis700.grange> (Guennadi Liakhovetski's message of "Thu, 14 Jul 2011 18:39:02 +0200 (CEST)")
Hi Guennadi,
On Thu, Jul 14 2011, Guennadi Liakhovetski wrote:
> There go two more bug-fixes for tmio on top of my earlier patches from
> today, so, should still be easy enough to trace. So, to pull them
> together, the previous ones were
>
> [PATCH v3] mmc: tmio: fix recursive spinlock, don't schedule with
> interrupts disabled
> [PATCH v3] mmc: tmio: maximize power saving
>
> And now follow
>
> [PATCH 1/2] mmc: tmio: fix a recently introduced bug in DMA code
> [PATCH 2/2] mmc: tmio: fix a deadlock
Pushed these four plus "mmc: sh_mmcif: maximize power saving" to
mmc-next for 3.1. Thanks!
By the way, feel free to send me a MAINTAINERS update taking over
TMIO if you'd like to; you've been doing the work. :-)
- Chris.
--
Chris Ball <cjb@laptop.org> <http://printf.net/>
One Laptop Per Child
next prev parent reply other threads:[~2011-07-14 19:27 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-14 16:39 [PATCH 0/2] mmc: tmio: two bug-fixes Guennadi Liakhovetski
2011-07-14 16:39 ` [PATCH 1/2] mmc: tmio: fix a recently introduced bug in DMA code Guennadi Liakhovetski
2011-07-14 16:39 ` [PATCH 2/2] mmc: tmio: fix a deadlock Guennadi Liakhovetski
2011-07-14 19:27 ` Chris Ball [this message]
2011-07-15 8:46 ` [PATCH 0/2] mmc: tmio: two bug-fixes Guennadi Liakhovetski
2011-08-27 21:40 ` Ian Molton
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=m2pqlcslx4.fsf@bob.laptop.org \
--to=cjb@laptop.org \
--cc=damm@opensource.se \
--cc=g.liakhovetski@gmx.de \
--cc=horms@verge.net.au \
--cc=ian@mnementh.co.uk \
--cc=linux-mmc@vger.kernel.org \
--cc=linux-sh@vger.kernel.org \
--cc=rjw@sisk.pl \
/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