From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: AnilKumar Ch <anilkumar@ti.com>
Cc: sameo@linux.intel.com, lrg@ti.com, linux-kernel@vger.kernel.org,
linux-omap@vger.kernel.org, nsekhar@ti.com
Subject: Re: [PATCH V3 1/2] MFD: TPS65217: Add new mfd device for TPS65217
Date: Sun, 8 Jan 2012 23:20:28 -0800 [thread overview]
Message-ID: <20120109072027.GD22134@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <1325670735-31208-1-git-send-email-anilkumar@ti.com>
On Wed, Jan 04, 2012 at 03:22:15PM +0530, AnilKumar Ch wrote:
> The TPS65217 chip is a power management IC for Portable Navigation Systems
> and Tablet Computing devices. It contains the following components:
Reviwed-by: Mark Brown <broonie@opensource.wolfsonmicro.com>
prev parent reply other threads:[~2012-01-09 7:20 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-04 9:52 [PATCH V3 1/2] MFD: TPS65217: Add new mfd device for TPS65217 AnilKumar Ch
2012-01-09 7:20 ` Mark Brown [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=20120109072027.GD22134@opensource.wolfsonmicro.com \
--to=broonie@opensource.wolfsonmicro.com \
--cc=anilkumar@ti.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=lrg@ti.com \
--cc=nsekhar@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).