From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Haojian Zhuang <haojian.zhuang@marvell.com>
Cc: johnpol@2ka.mipt.ru, sameo@linux.intel.com, a.zummo@towertech.it,
lrg@slimlogic.co.uk, dmitry.torokhov@gmail.com, dtor@mail.ru,
rpurdie@rpsys.net, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] mfd: adopt mfd_data in 88pm860x regulator
Date: Tue, 8 Mar 2011 23:24:19 +0000 [thread overview]
Message-ID: <20110308232419.GA2717@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <1299512600-29047-3-git-send-email-haojian.zhuang@marvell.com>
On Mon, Mar 07, 2011 at 11:43:11PM +0800, Haojian Zhuang wrote:
> Copy 88pm860x platform data into different mfd_data structure for
> regulator driver. So move the identification of device node from
> regulator driver to mfd driver.
>
> Signed-off-by: Haojian Zhuang <haojian.zhuang@marvell.com>
Acked-by: Mark Brown <broonie@opensource.wolfsonmicro.com>
but if there's any in-tree users of the device I'd expect they need
their platform data updated?
next prev parent reply other threads:[~2011-03-08 23:24 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-07 15:43 [PATCH] mfd: adopt mfd_data in 88pm860x backlight Haojian Zhuang
2011-03-07 15:43 ` [PATCH] mfd: adopt mfd_data in 88pm860x led Haojian Zhuang
2011-03-07 15:43 ` [PATCH] mfd: adopt mfd_data in 88pm860x regulator Haojian Zhuang
2011-03-07 15:43 ` [PATCH] mfd: adopt mfd_data in 88pm860x Haojian Zhuang
2011-03-07 15:43 ` [PATCH] mfd: add workqueue thread into 88pm860x Haojian Zhuang
2011-03-07 15:43 ` [PATCH] input: touchscreen: use polling mode in 88pm860x Haojian Zhuang
2011-03-07 15:43 ` [PATCH] input: touchscreen: move initialization " Haojian Zhuang
2011-03-07 15:43 ` [PATCH] mfd: append additional read write on 88pm860x Haojian Zhuang
2011-03-07 15:43 ` [PATCH] rtc: add 88pm860x rtc Haojian Zhuang
2011-03-07 15:43 ` [PATCH] input: set the long press detection in 88pm860x onkey Haojian Zhuang
2011-03-07 15:43 ` [PATCH] w1: add DS278x slave driver Haojian Zhuang
2011-03-07 15:43 ` [PATCH] mfd: pxa-w1: MFD driver for PXA 1wire control + DS1WM chip Haojian Zhuang
2011-03-14 11:28 ` Samuel Ortiz
2011-03-14 12:34 ` Haojian Zhuang
2011-03-14 19:55 ` Jean-Francois Dagenais
2011-03-13 6:45 ` [PATCH] input: set the long press detection in 88pm860x onkey Dmitry Torokhov
2011-03-14 10:51 ` [PATCH] rtc: add 88pm860x rtc Samuel Ortiz
2011-03-14 13:09 ` Haojian Zhuang
2011-03-14 11:25 ` [PATCH] mfd: append additional read write on 88pm860x Samuel Ortiz
2011-03-13 6:44 ` [PATCH] input: touchscreen: use polling mode in 88pm860x Dmitry Torokhov
2011-03-14 12:41 ` Haojian Zhuang
2011-03-15 5:02 ` Dmitry Torokhov
2011-03-13 6:38 ` [PATCH] mfd: add workqueue thread into 88pm860x Dmitry Torokhov
2011-03-14 11:24 ` [PATCH] mfd: adopt mfd_data in 88pm860x Samuel Ortiz
2011-03-08 23:24 ` Mark Brown [this message]
2011-03-14 11:23 ` [PATCH] mfd: adopt mfd_data in 88pm860x regulator Samuel Ortiz
2011-03-14 11:23 ` [PATCH] mfd: adopt mfd_data in 88pm860x led Samuel Ortiz
2011-03-14 10:56 ` [PATCH] mfd: adopt mfd_data in 88pm860x backlight Samuel Ortiz
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=20110308232419.GA2717@opensource.wolfsonmicro.com \
--to=broonie@opensource.wolfsonmicro.com \
--cc=a.zummo@towertech.it \
--cc=dmitry.torokhov@gmail.com \
--cc=dtor@mail.ru \
--cc=haojian.zhuang@marvell.com \
--cc=johnpol@2ka.mipt.ru \
--cc=linux-kernel@vger.kernel.org \
--cc=lrg@slimlogic.co.uk \
--cc=rpurdie@rpsys.net \
--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