From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: "AnilKumar, Chimata" <anilkumar@ti.com>
Cc: "sameo@linux.intel.com" <sameo@linux.intel.com>,
"Girdwood, Liam" <lrg@ti.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>,
"devicetree-discuss@lists.ozlabs.org"
<devicetree-discuss@lists.ozlabs.org>,
"grant.likely@secretlab.ca" <grant.likely@secretlab.ca>
Subject: Re: [PATCH v2 1/3] regulator: tps65217: Add device tree support
Date: Fri, 13 Jul 2012 10:54:54 +0100 [thread overview]
Message-ID: <20120713095454.GB4215@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <331ABD5ECB02734CA317220B2BBEABC13E9F61CC@DBDE01.ent.ti.com>
[-- Attachment #1: Type: text/plain, Size: 236 bytes --]
On Fri, Jul 13, 2012 at 05:43:30AM +0000, AnilKumar, Chimata wrote:
> Thanks much, are you going to push reset of the patches in this series?
No, there's no dependency so I'd expect them to be applied by the
architecture maintainers.
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2012-07-13 9:54 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-10 11:09 [PATCH v2 0/3] Add device tree support for AM33XX regulators AnilKumar Ch
2012-07-10 11:09 ` [PATCH v2 1/3] regulator: tps65217: Add device tree support AnilKumar Ch
2012-07-12 17:28 ` Mark Brown
[not found] ` <20120712172836.GR7256-yzvPICuk2AATkU/dhu1WVueM+bqZidxxQQ4Iyu8u01E@public.gmane.org>
2012-07-13 5:43 ` AnilKumar, Chimata
2012-07-13 9:54 ` Mark Brown [this message]
2012-07-16 12:35 ` AnilKumar, Chimata
[not found] ` <1341918584-28004-1-git-send-email-anilkumar-l0cyMroinI0@public.gmane.org>
2012-07-10 11:09 ` [PATCH v2 2/3] ARM: OMAP2+: AM33XX: Add tps65910 device tree data AnilKumar Ch
2012-07-10 11:09 ` [PATCH v2 3/3] ARM: OMAP2+: AM33XX: Add tps65217 " AnilKumar Ch
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=20120713095454.GB4215@opensource.wolfsonmicro.com \
--to=broonie@opensource.wolfsonmicro.com \
--cc=anilkumar@ti.com \
--cc=devicetree-discuss@lists.ozlabs.org \
--cc=grant.likely@secretlab.ca \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=lrg@ti.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).