From: Laxman Dewangan <ldewangan@nvidia.com>
To: Samuel Ortiz <sameo@linux.intel.com>
Cc: "broonie@opensource.wolfsonmicro.com"
<broonie@opensource.wolfsonmicro.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, 4 Feb 2013 09:10:51 +0530 [thread overview]
Message-ID: <510F2DC3.2060803@nvidia.com> (raw)
In-Reply-To: <20130203223304.GB24304@sortiz-mobl>
On Monday 04 February 2013 04:03 AM, Samuel Ortiz wrote:
> Hi Laxman,
>
> On Sun, Feb 03, 2013 at 03:19:31PM +0100, Samuel Ortiz wrote:
>> Hi Laxman,
>>
>> On Fri, Dec 28, 2012 at 02:59:37PM +0530, Laxman Dewangan wrote:
>>> The patch series add DT support on TPS65090 device.
>>>
>>> Also remove the suspend/resume implementation as it duplicates with
>>> irq_suspend/irq_resume().
>>>
>>> Laxman Dewangan (4):
>>> mfd: tps65090: add DT support for tps65090
>>> regulator: tps65090: add DT support
>>> mfd: tps65090: Pass irq domain when adding mfd sub devices
>>> mfd: tps65090: remove suspend/resume callbacks
>>>
>>> .../devicetree/bindings/regulator/tps65090.txt | 121 ++++++++++++++++++++
>>> drivers/mfd/tps65090.c | 77 ++++++++----
>>> drivers/regulator/tps65090-regulator.c | 96 +++++++++++++++-
>>> include/linux/mfd/tps65090.h | 1 +
>>> 4 files changed, 266 insertions(+), 29 deletions(-)
>>> create mode 100644 Documentation/devicetree/bindings/regulator/tps65090.txt
>> All 4 patches applied to my for-next branch, thanks.
> Sorry for the confusion: I took v2 of your patchset, skipping the regulator
> patch who will go through Mark's tree.
Thank you very much. The regulator patch is already applied in Mark's tree.
Thanks,
Laxman
prev parent reply other threads:[~2013-02-04 3:40 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
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 [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=510F2DC3.2060803@nvidia.com \
--to=ldewangan@nvidia.com \
--cc=broonie@opensource.wolfsonmicro.com \
--cc=devicetree-discuss@lists.ozlabs.org \
--cc=grant.likely@secretlab.ca \
--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).