From: Chao Xie <chao.xie@marvell.com>
To: <linux-kernel@vger.kernel.org>, <sameo@linux.intel.com>,
<xiechao.mail@gmail.com>
Cc: Chao Xie <chao.xie@marvell.com>
Subject: [PATCH 0/4] mfd: 88pn80x: bug fix and device tree support
Date: Mon, 29 Jul 2013 04:29:23 -0400 [thread overview]
Message-ID: <1375086567-10705-1-git-send-email-chao.xie@marvell.com> (raw)
There are 4 patches.
1. Bug fix.
mfd: 88pm800: Fix the bug that pdata may be NULL
mfd: 88pm805: Fix the bug that pdata may be NULL
Above patches fix the bug that pdata may be NULL when driver uses it.
2. Device tree support
mfd: 88pm800: add device tree support
mfd: 88pm805: add device tree support
Add device tree support for 88pm800 and 88pm805
Chao Xie (4):
mfd: 88pm800: Fix the bug that pdata may be NULL
mfd: 88pm805: Fix the bug that pdata may be NULL
mfd: 88pm800: add device tree support
mfd: 88pm805: add device tree support
Documentation/devicetree/bindings/mfd/88pm800.c | 55 +++++++++++++++++++
Documentation/devicetree/bindings/mfd/88pm805.c | 15 +++++
drivers/mfd/88pm800.c | 65 +++++++++++++++++++++--
drivers/mfd/88pm805.c | 10 +++-
4 files changed, 140 insertions(+), 5 deletions(-)
create mode 100644 Documentation/devicetree/bindings/mfd/88pm800.c
create mode 100644 Documentation/devicetree/bindings/mfd/88pm805.c
--
1.7.4.1
next reply other threads:[~2013-07-29 8:30 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-29 8:29 Chao Xie [this message]
2013-07-29 8:29 ` [PATCH 1/4] mfd: 88pm800: Fix the bug that pdata may be NULL Chao Xie
2013-07-29 8:29 ` [PATCH 2/4] mfd: 88pm805: " Chao Xie
2013-07-29 8:29 ` [PATCH 3/4] mfd: 88pm800: add device tree support Chao Xie
2013-07-29 8:29 ` [PATCH 4/4] mfd: 88pm805: " Chao Xie
-- strict thread matches above, loose matches on Subject: below --
2013-08-14 8:28 [PATCH 0/4] mfd: 88pn80x: bug fix and " Chao Xie
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=1375086567-10705-1-git-send-email-chao.xie@marvell.com \
--to=chao.xie@marvell.com \
--cc=linux-kernel@vger.kernel.org \
--cc=sameo@linux.intel.com \
--cc=xiechao.mail@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).