From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Laxman Dewangan <ldewangan@nvidia.com>
Cc: "sameo@linux.intel.com" <sameo@linux.intel.com>,
"grant.likely@secretlab.ca" <grant.likely@secretlab.ca>,
"rob.herring@calxeda.com" <rob.herring@calxeda.com>,
"rob@landley.net" <rob@landley.net>, "lrg@ti.com" <lrg@ti.com>,
"devicetree-discuss@lists.ozlabs.org"
<devicetree-discuss@lists.ozlabs.org>,
"linux-doc@vger.kernel.org" <linux-doc@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 0/4] mfd/regulator: tps65090: add DT support and suspend/resume cleanups
Date: Mon, 14 Jan 2013 08:29:38 +0900 [thread overview]
Message-ID: <20130113232937.GQ5041@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <50EC1046.3000701@nvidia.com>
[-- Attachment #1: Type: text/plain, Size: 479 bytes --]
On Tue, Jan 08, 2013 at 05:55:42PM +0530, Laxman Dewangan wrote:
> I am not sure that the patches are created on correct sequence for
> adapting this in regulator subsystem and mfd subsystem.
> Can you please review whether the changes split is fine or not?
> Idea was to make independent patch for mfd and regulator so that
> they can apply independently.
The addition of pdata to the header means that they can't be applied
independantly but that's not the end of the world.
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2013-01-13 23:29 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-28 9:29 [PATCH 0/4] mfd/regulator: tps65090: add DT support and suspend/resume cleanups Laxman Dewangan
2012-12-28 9:29 ` [PATCH 1/4] mfd: tps65090: add DT support for tps65090 Laxman Dewangan
[not found] ` <1356686981-4152-1-git-send-email-ldewangan-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
2012-12-28 9:29 ` [PATCH 2/4] regulator: tps65090: add DT support Laxman Dewangan
2013-01-14 13:32 ` Mark Brown
2012-12-28 9:29 ` [PATCH 3/4] mfd: tps65090: Pass irq domain when adding mfd sub devices Laxman Dewangan
2012-12-28 9:29 ` [PATCH 4/4] mfd: tps65090: remove suspend/resume callbacks Laxman Dewangan
2013-01-14 13:42 ` Mark Brown
2013-01-08 12:25 ` [PATCH 0/4] mfd/regulator: tps65090: add DT support and suspend/resume cleanups Laxman Dewangan
2013-01-13 23:29 ` Mark Brown [this message]
2013-02-03 17:01 ` Samuel Ortiz
[not found] ` <20130203141931.GA8476@sortiz-mobl>
2013-02-03 22:33 ` Samuel Ortiz
2013-02-04 3:40 ` Laxman Dewangan
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=20130113232937.GQ5041@opensource.wolfsonmicro.com \
--to=broonie@opensource.wolfsonmicro.com \
--cc=devicetree-discuss@lists.ozlabs.org \
--cc=grant.likely@secretlab.ca \
--cc=ldewangan@nvidia.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lrg@ti.com \
--cc=rob.herring@calxeda.com \
--cc=rob@landley.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;
as well as URLs for NNTP newsgroup(s).