From: Laxman Dewangan <ldewangan@nvidia.com>
To: Samuel Ortiz <sameo@linux.intel.com>
Cc: "grant.likely@secretlab.ca" <grant.likely@secretlab.ca>,
"linus.walleij@stericsson.com" <linus.walleij@stericsson.com>,
"broonie@opensource.wolfsonmicro.com"
<broonie@opensource.wolfsonmicro.com>,
"jedu@slimlogic.co.uk" <jedu@slimlogic.co.uk>,
"lrg@slimlogic.co.uk" <lrg@slimlogic.co.uk>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 0/4] mfd:tps65910: use devm_* and register gpio as platform driver
Date: Fri, 11 May 2012 18:48:00 +0530 [thread overview]
Message-ID: <4FAD1188.7000706@nvidia.com> (raw)
In-Reply-To: <20120511131454.GI1214@sortiz-mobl>
On Friday 11 May 2012 06:44 PM, Samuel Ortiz wrote:
> Hi Laxman,
>
> On Wed, May 09, 2012 at 06:40:53PM +0530, Laxman Dewangan wrote:
>> This series does cleanup in the mfd/tps65910 as follows:
>> - Do not cache the register when initailizing regmap. Cache when
>> actually when we need it.
>> - Convert the allocation to use devm_* apis.
>> - Move the gpio as platform driver and register it as mfd sub devices.
>>
>> Laxman Dewangan (4):
>> mfd: tps65910: cache register when we need it
>> Remove the chaching of register in regmap initialization.
>>
>> mfd: tps65910: convert all allocation to devm_*
>> Convert the allocation to use devm_* apis.
>>
>> mfd: tps65910: register gpio as mfd device
>> gpio: tps65910: move this as platform driver
>> Above two patch to make gpio driver as platform driver and register
>> as mfd sub device from core driver.
>>
> I applied patches 1, 2 and 3. Patch #4 does not apply cleanly to my for-next
> branch, could you please rebase it ?
> Also, having Grant's ACK for it would be nice.
Thanks for taking care.
I will create a new patch based on your tree if Grant is OK with this.
prev parent reply other threads:[~2012-05-11 13:22 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-09 13:10 [PATCH 0/4] mfd:tps65910: use devm_* and register gpio as platform driver Laxman Dewangan
2012-05-09 13:10 ` [PATCH 1/4] mfd: tps65910: cache register when we need it Laxman Dewangan
2012-05-09 14:55 ` Mark Brown
2012-05-09 13:10 ` [PATCH 2/4] mfd: tps65910: convert all allocation to devm_* Laxman Dewangan
2012-05-09 15:11 ` Mark Brown
2012-05-09 13:10 ` [PATCH 3/4] mfd: tps65910: register gpio as mfd device Laxman Dewangan
2012-05-09 13:10 ` [PATCH 4/4] gpio: tps65910: move this as platform driver Laxman Dewangan
2012-05-11 17:40 ` Grant Likely
2012-05-11 19:08 ` Mark Brown
2012-05-11 13:14 ` [PATCH 0/4] mfd:tps65910: use devm_* and register gpio " Samuel Ortiz
2012-05-11 13:18 ` Laxman Dewangan [this message]
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=4FAD1188.7000706@nvidia.com \
--to=ldewangan@nvidia.com \
--cc=broonie@opensource.wolfsonmicro.com \
--cc=grant.likely@secretlab.ca \
--cc=jedu@slimlogic.co.uk \
--cc=linus.walleij@stericsson.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lrg@slimlogic.co.uk \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.