From: Simon Horman <horms@verge.net.au>
To: Guennadi Liakhovetski <g.liakhovetski@gmx.de>,
Magnus Damm <magnus.damm@gmail.com>
Cc: Ian Molton <ian@mnementh.co.uk>, Chris Ball <cjb@laptop.org>,
Paul Mundt <lethal@linux-sh.org>,
linux-sh@vger.kernel.org, linux-mmc@vger.kernel.org
Subject: mmc: sdhi, tmio: updates
Date: Mon, 09 May 2011 00:55:10 +0000 [thread overview]
Message-ID: <1304902516-14150-1-git-send-email-horms@verge.net.au> (raw)
Hi,
there are currently a number of patches floating around for
TMIO and SDHI. This post is an attempt to collect together the latest
version of each of these patches.
I have also changed the author of the following patches
from Magnus to Guennadi to reflect that Guennadi wrote
the most recent version. In each case I have noted that the patch
is based on work by Magnus and as appropriate work by myself.
mmc: tmio / sdhi: break out interrupt request/free
mmc: sdhi: support up to 3 interrupt sources
I have also removed Signed-off-by lines from the following
patches which were not supplied by the person whose name
features in the Signed-off-by line.
mmc: sdhi: support up to 3 interrupt sources
mmc: tmio / sdhi: break out interrupt request/free
Or in other words, I removed Magnus's Signed-off-by lines
where Guennadi had posted a revised version of the patch.
Magnus, could you add a Reviewed-by, Acked-by
or Signed-off-by as you feel is appropriate?
For reference the patches are available at:
git://git.kernel.org/pub/scm/linux/kernel/git/horms/shmobile-2.6.git sdhi-next
Which is based on:
git://git.kernel.org/pub/scm/linux/kernel/git/cjb/mmc.git mmc/mmc-next
Guennadi Liakhovetski (4):
MMC: protect the tmio_mmc driver against a theoretical race
mmc: Add runtime and system-wide PM to the TMIO MMC driver
mmc: tmio / sdhi: break out interrupt request/free
mmc: sdhi: support up to 3 interrupt sources
Magnus Damm (2):
mmc: sdhi: no need for special interrupt flags
mmc: sdhi: print out something useful
drivers/mmc/host/sh_mobile_sdhi.c | 44 ++++++++++++-
drivers/mmc/host/tmio_mmc.c | 32 ++++++---
drivers/mmc/host/tmio_mmc.h | 13 ++++-
drivers/mmc/host/tmio_mmc_dma.c | 21 ++++---
drivers/mmc/host/tmio_mmc_pio.c | 128 +++++++++++++++++++++++++++++++------
5 files changed, 195 insertions(+), 43 deletions(-)
next reply other threads:[~2011-05-09 0:55 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-09 0:55 Simon Horman [this message]
2011-05-09 0:55 ` [PATCH 1/6] MMC: protect the tmio_mmc driver against a theoretical race Simon Horman
2011-05-09 0:55 ` [PATCH 2/6] mmc: Add runtime and system-wide PM to the TMIO MMC driver Simon Horman
2011-05-09 0:55 ` [PATCH 3/6] mmc: tmio / sdhi: break out interrupt request/free Simon Horman
2011-05-09 0:55 ` [PATCH 4/6] mmc: sdhi: no need for special interrupt flags Simon Horman
2011-05-09 0:55 ` [PATCH 5/6] mmc: sdhi: print out something useful Simon Horman
2011-05-09 0:55 ` [PATCH 6/6] mmc: sdhi: support up to 3 interrupt sources Simon Horman
2011-05-09 9:53 ` mmc: sdhi, tmio: updates Simon Horman
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=1304902516-14150-1-git-send-email-horms@verge.net.au \
--to=horms@verge.net.au \
--cc=cjb@laptop.org \
--cc=g.liakhovetski@gmx.de \
--cc=ian@mnementh.co.uk \
--cc=lethal@linux-sh.org \
--cc=linux-mmc@vger.kernel.org \
--cc=linux-sh@vger.kernel.org \
--cc=magnus.damm@gmail.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 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).