From: Mark Brown <broonie@kernel.org>
To: Keerthy <j-keerthy@ti.com>
Cc: linux-omap@vger.kernel.org, lgirdwood@gmail.com,
linux-kernel@vger.kernel.org, sameo@linux.intel.com,
lee.jones@linaro.org
Subject: Re: [PATCH v2 0/9] mfd: tps65917: Add support for for TPS65917 PMIC
Date: Mon, 23 Jun 2014 12:32:25 +0100 [thread overview]
Message-ID: <20140623113225.GC24291@sirena.org.uk> (raw)
In-Reply-To: <1403085540-20014-1-git-send-email-j-keerthy@ti.com>
[-- Attachment #1: Type: text/plain, Size: 226 bytes --]
On Wed, Jun 18, 2014 at 03:28:51PM +0530, Keerthy wrote:
> The TPS65917 chip is a power management IC for Portable Navigation Systems
> and Tablet Computing devices. It contains the following components:
Applied all, thanks.
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
prev parent reply other threads:[~2014-06-23 11:32 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-18 9:58 Keerthy
2014-06-18 9:58 ` [PATCH v2 1/9] mfd: Add DT bindings for tps65917 PMIC Keerthy
2014-06-18 9:58 ` [PATCH v2 2/9] regulator: palmas: Add tps65917 compatible string Keerthy
2014-06-18 9:58 ` [PATCH v2 3/9] mfd: palmas: Add tps65917 specific definitions and enums Keerthy
2014-06-18 9:58 ` [PATCH v2 4/9] mfd: palmas: Add tps65917 support Keerthy
2014-06-18 9:58 ` [PATCH v2 5/9] regulator: palmas: Shift the reg_info structure definition to the header file Keerthy
2014-06-18 9:58 ` [PATCH v2 6/9] mfd: palmas: shift the palmas_sleep_requestor_info " Keerthy
2014-06-18 9:58 ` [PATCH v2 7/9] regulator: palmas: Add palmas_pmic_driver_data structure Keerthy
2014-06-27 8:20 ` Lee Jones
2014-06-18 9:58 ` [PATCH v2 8/9] regulator: palmas: add driver data and modularize the probe Keerthy
2014-06-27 8:23 ` Lee Jones
2014-06-27 9:36 ` Keerthy
2014-06-18 9:59 ` [PATCH v2 9/9] regulator: palmas: Add tps65917 PMIC support Keerthy
2014-06-23 11:32 ` 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=20140623113225.GC24291@sirena.org.uk \
--to=broonie@kernel.org \
--cc=j-keerthy@ti.com \
--cc=lee.jones@linaro.org \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--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
all inboxes | Powered by JetHome®