From: andrew@lunn.ch (Andrew Lunn)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 0/5] mmc: mvsdio: use devm_ API to simplify/correct error paths.
Date: Wed, 16 Jan 2013 14:13:55 +0100 [thread overview]
Message-ID: <1358342040-7130-1-git-send-email-andrew@lunn.ch> (raw)
Russell King pointed out a number of issues with the probe code in the
mvsdio driver and supplied a patch. This patchset uses a modified
version, converting resource allocations to devm API calls, and fixes
the error paths. The patches that then follow are from Thomas
Petazzoni making other cleanups and adding device tree. These patches
needed some changes after the swap to devm. The patches here replace
the earlier submitted patches with the same Subject.
Andrew Lunn (1):
mmc: mvsdio: use devm_ API to simplify/correct error paths.
Thomas Petazzoni (4):
mmc: mvsdio: use slot-gpio infrastructure for write protect gpio
mmc: mvsdio: use slot-gpio for card detect gpio
mmc: mvsdio: implement a Device Tree binding
mmc: mvsdio: add pinctrl integration
.../devicetree/bindings/mmc/orion-sdio.txt | 17 ++
drivers/mmc/host/mvsdio.c | 187 ++++++++------------
2 files changed, 93 insertions(+), 111 deletions(-)
create mode 100644 Documentation/devicetree/bindings/mmc/orion-sdio.txt
--
1.7.10.4
next reply other threads:[~2013-01-16 13:13 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-16 13:13 Andrew Lunn [this message]
2013-01-16 13:13 ` [PATCH 1/5] mmc: mvsdio: use devm_ API to simplify/correct error paths Andrew Lunn
2013-01-23 1:09 ` Jason Cooper
2013-01-16 13:13 ` [PATCH 2/5] mmc: mvsdio: use slot-gpio infrastructure for write protect gpio Andrew Lunn
2013-01-16 13:13 ` [PATCH 3/5] mmc: mvsdio: use slot-gpio for card detect gpio Andrew Lunn
2013-01-16 13:13 ` [PATCH 4/5] mmc: mvsdio: implement a Device Tree binding Andrew Lunn
2013-01-16 13:14 ` [PATCH 5/5] mmc: mvsdio: add pinctrl integration Andrew Lunn
2013-01-23 1:44 ` [PATCH 0/5] mmc: mvsdio: use devm_ API to simplify/correct error paths 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=1358342040-7130-1-git-send-email-andrew@lunn.ch \
--to=andrew@lunn.ch \
--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).