From: Haojian Zhuang <haojian.zhuang@gmail.com>
To: Qing Xu <qingx@marvell.com>
Cc: Samuel Ortiz <sameo@linux.intel.com>,
Grant Likely <grant.likely@secretlab.ca>,
Rob Herring <rob.herring@calxeda.com>,
Chao Xie <cxie4@marvell.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"devicetree-discuss@lists.ozlabs.org"
<devicetree-discuss@lists.ozlabs.org>
Subject: Re: [PATCH 0/7] mfd: update on max8925 for DT support
Date: Mon, 4 Feb 2013 09:05:09 +0800 [thread overview]
Message-ID: <CAN1soZycHE97uAFcJYxxkUXc_66JJgKUFRxed1sii9VswTdXDQ@mail.gmail.com> (raw)
In-Reply-To: <50C8228B.7040702@marvell.com>
On Wed, Dec 12, 2012 at 2:22 PM, Qing Xu <qingx@marvell.com> wrote:
> On 12/04/2012 03:11 PM, Haojian Zhuang wrote:
>>
>> On Thu, Nov 29, 2012 at 1:54 PM, Qing Xu <qingx@marvell.com> wrote:
>>>
>>> On 11/23/2012 05:09 PM, Haojian Zhuang wrote:
>>>>
>>>> On Tue, Nov 6, 2012 at 3:35 PM, Qing Xu <qingx@marvell.com> wrote:
>>>>>
>>>>> From: Qing Xu <qingx@marvell.com>
>>>>>
>>>>> 1. add irqdomain for max8925, it is necessary for dt support
>>>>> 2. bug fix in max8925 mfd devices'irq base and device registry failure
>>>>> 3. support DT for max8925 mfd devices
>>>>>
>>>>> Qing Xu (7):
>>>>> mfd: max8925: add irqdomain for dt
>>>>> mfd: max8925: fix mfd device register failure
>>>>> mfd: max8925: fix onkey driver irq base
>>>>> mfd: max8925: support dt for power supply
>>>>> mfd: max8925: support dt for regulator
>>>>> mfd: max8925: support dt for backlight
>>>>> mfd: max8925: add dts
>>>>>
>>>>> arch/arm/boot/dts/mmp2-brownstone.dts | 166
>>>>> +++++++++++++++++++++++++++++++++
>>>>> arch/arm/boot/dts/mmp2.dtsi | 4 +-
>>>>> drivers/input/misc/max8925_onkey.c | 3 -
>>>>> drivers/mfd/max8925-core.c | 107 +++++++++++++--------
>>>>> drivers/mfd/max8925-i2c.c | 32 ++++++-
>>>>> drivers/power/max8925_power.c | 57 ++++++++++-
>>>>> drivers/regulator/max8925-regulator.c | 35 +++++++-
>>>>> drivers/video/backlight/max8925_bl.c | 31 ++++++-
>>>>> include/linux/mfd/max8925.h | 12 ++-
>>>>> 9 files changed, 389 insertions(+), 58 deletions(-)
>>>>>
>>>> No document on devicetree binding?
>>>
>>> I added a new patch of "Documentation: add docs for max8925 dt",
>>> please help to review, thanks a lot!
>>
>> Acked.
>>
>> Samuel,
>> How do you think about this patch series? From my view, it's ok.
>>
>> Best Regards
>> Haojian
>
>
>
>
> Samuel,
>
> Do you have any comments on these patches? Could they be merged?
>
> Thanks a lot!
> Qing
>
>
Hi Samuel,
Are they merged into your git tree?
Best Regards
Haojian
next prev parent reply other threads:[~2013-02-04 1:05 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-06 7:35 [PATCH 0/7] mfd: update on max8925 for DT support Qing Xu
2012-11-23 7:12 ` Qing Xu
[not found] ` <1352187305-9660-1-git-send-email-qingx-eYqpPyKDWXRBDgjK7y7TUQ@public.gmane.org>
2012-11-23 9:09 ` Haojian Zhuang
2012-11-29 5:54 ` Qing Xu
2012-12-04 7:11 ` Haojian Zhuang
2012-12-12 6:22 ` Qing Xu
2013-02-04 1:05 ` Haojian Zhuang [this message]
2013-02-04 11:32 ` Samuel Ortiz
2013-02-04 15:41 ` Haojian Zhuang
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=CAN1soZycHE97uAFcJYxxkUXc_66JJgKUFRxed1sii9VswTdXDQ@mail.gmail.com \
--to=haojian.zhuang@gmail.com \
--cc=cxie4@marvell.com \
--cc=devicetree-discuss@lists.ozlabs.org \
--cc=grant.likely@secretlab.ca \
--cc=linux-kernel@vger.kernel.org \
--cc=qingx@marvell.com \
--cc=rob.herring@calxeda.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;
as well as URLs for NNTP newsgroup(s).