From: Laxman Dewangan <ldewangan@nvidia.com>
To: Mark Brown <broonie@opensource.wolfsonmicro.com>
Cc: "sameo@linux.intel.com" <sameo@linux.intel.com>,
"lrg@ti.com" <lrg@ti.com>, Stephen Warren <swarren@nvidia.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] mfd: tps6586x: move regulator dt parsing to regulator driver
Date: Thu, 15 Nov 2012 17:52:27 -0500 [thread overview]
Message-ID: <50A5722B.9080707@nvidia.com> (raw)
In-Reply-To: <20121115052346.GF7599@opensource.wolfsonmicro.com>
On 11/15/2012 12:23 AM, Mark Brown wrote:
> * PGP Signed by an unknown key
>
> On Thu, Oct 18, 2012 at 07:36:09PM +0530, Laxman Dewangan wrote:
>> Moving regulator node parsing to regulator driver in place
>> of parsing it on mfd driver.
> Applied, thanks.
>
Thanks, I hope it will not create conflict with Samuel's mfd subsystem
tree as some changes on same file got merged recently in mfd subsystem.
prev parent reply other threads:[~2012-11-15 22:52 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-18 14:06 [PATCH] mfd: tps6586x: move regulator dt parsing to regulator driver Laxman Dewangan
2012-11-15 5:23 ` Mark Brown
2012-11-15 22:52 ` 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=50A5722B.9080707@nvidia.com \
--to=ldewangan@nvidia.com \
--cc=broonie@opensource.wolfsonmicro.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lrg@ti.com \
--cc=sameo@linux.intel.com \
--cc=swarren@nvidia.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).