From: Charles Keepax <ckeepax@opensource.wolfsonmicro.com>
To: lee.jones@linaro.org
Cc: sameo@linux.intel.com, patches@opensource.wolfsonmicro.com,
linux-kernel@vger.kernel.org
Subject: [PATCH 0/5] Arizona clean up driver removal and error paths
Date: Mon, 2 Jun 2014 09:50:38 +0100 [thread overview]
Message-ID: <1401699043-16835-1-git-send-email-ckeepax@opensource.wolfsonmicro.com> (raw)
Several small fixes to the error and driver removal paths
for the arizona devices. This series will likely need to be
applied onto of my earlier "wm5110 Interrupt Updates" series
to apply cleanly, please let me know if I need to resend
that. It would also be possible to rebase them the other way
round although that will obviously require me to resend the
interrupt series.
Thanks,
Charles
Charles Keepax (5):
mfd: arizona: Disable PM runtime at start of driver removal
mfd: arizona: Disable DCVDD before we destroy the MFD
mfd: arizona: Don't use devres for DCVDD
mfd: arizona: Use num_core_supplies in arizona_dev_exit
mfd: arizona: Lower ARIZONA_MAX_CORE_SUPPLIES to 2
drivers/mfd/arizona-core.c | 18 ++++++++++++------
include/linux/mfd/arizona/core.h | 2 +-
2 files changed, 13 insertions(+), 7 deletions(-)
--
1.7.2.5
next reply other threads:[~2014-06-02 8:58 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-02 8:50 Charles Keepax [this message]
2014-06-02 8:50 ` [PATCH 1/5] mfd: arizona: Disable PM runtime at start of driver removal Charles Keepax
2014-06-17 14:33 ` Lee Jones
2014-06-02 8:50 ` [PATCH 2/5] mfd: arizona: Disable DCVDD before we destroy the MFD Charles Keepax
2014-06-17 14:33 ` Lee Jones
2014-06-02 8:50 ` [PATCH 3/5] mfd: arizona: Don't use devres for DCVDD Charles Keepax
2014-06-17 14:36 ` Lee Jones
2014-06-17 15:17 ` Charles Keepax
2014-06-02 8:50 ` [PATCH 4/5] mfd: arizona: Use num_core_supplies in arizona_dev_exit Charles Keepax
2014-06-17 14:36 ` Lee Jones
2014-06-02 8:50 ` [PATCH 5/5] mfd: arizona: Lower ARIZONA_MAX_CORE_SUPPLIES to 2 Charles Keepax
2014-06-17 14:36 ` Lee Jones
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=1401699043-16835-1-git-send-email-ckeepax@opensource.wolfsonmicro.com \
--to=ckeepax@opensource.wolfsonmicro.com \
--cc=lee.jones@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=patches@opensource.wolfsonmicro.com \
--cc=sameo@linux.intel.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