From: Kevin Hilman <khilman@deeprootsystems.com>
To: "Krishnamoorthy, Balaji T" <balajitk@ti.com>
Cc: "linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>,
"Shilimkar, Santosh" <santosh.shilimkar@ti.com>,
"Nayak, Rajendra" <rnayak@ti.com>,
"a.zummo@towertech.it" <a.zummo@towertech.it>,
"p_gortmaker@yahoo.com" <p_gortmaker@yahoo.com>,
"sameo@linux.intel.com" <sameo@linux.intel.com>,
"tony@atomide.com" <tony@atomide.com>
Subject: Re: [PATCH v3 0/4] TWL6030 patch series
Date: Thu, 01 Oct 2009 11:37:53 -0700 [thread overview]
Message-ID: <87ocorc64e.fsf@deeprootsystems.com> (raw)
In-Reply-To: <19F8576C6E063C45BE387C64729E73940436CF8BFA@dbde02.ent.ti.com> (Balaji T. Krishnamoorthy's message of "Thu\, 1 Oct 2009 17\:52\:04 +0530")
"Krishnamoorthy, Balaji T" <balajitk@ti.com> writes:
> This patch series v3 incorporates comments received earlier[1].
>
> The upcoming TWL6030 is companion chip for OMAP4 like the current TWL4030
> for OMAP3. This patch series adds support for TWL6030 irq framework, and
> driver support for RTC and regulator.
>
> These patches has dependancy on TWL patch series[2]
> [PATCH v3 01/04] OMAP4: PMIC: Add support for twl6030 irq framework
> [PATCH v3 02/04] OMAP4: PMIC: Add support for twl6030 RTC
> [PATCH v3 03/04] OMAP4: PMIC: Add support for twl6030 regulators
> [PATCH v3 04/04] OMAP4: PMIC: Update TWL mfd driver to create twl6030
> Regulators
>
> [1] http://marc.info/?l=linux-omap&m=125050037530307&w=2
> [RFC][PATCH 0/4] TWL6030 patch series
>
> [2] http://marc.info/?l=linux-omap&m=125439874001377&w=2
> [PATCH v3 0/4] TWL patch series
In the future, please report what platforms this was tested on and
whether it was just compile tested, boot tested or actually
functionally tested.
Thanks,
Kevin
next prev parent reply other threads:[~2009-10-01 18:37 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-01 12:22 [PATCH v3 0/4] TWL6030 patch series Krishnamoorthy, Balaji T
2009-10-01 18:37 ` Kevin Hilman [this message]
2009-10-02 6:33 ` Shilimkar, Santosh
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=87ocorc64e.fsf@deeprootsystems.com \
--to=khilman@deeprootsystems.com \
--cc=a.zummo@towertech.it \
--cc=balajitk@ti.com \
--cc=linux-omap@vger.kernel.org \
--cc=p_gortmaker@yahoo.com \
--cc=rnayak@ti.com \
--cc=sameo@linux.intel.com \
--cc=santosh.shilimkar@ti.com \
--cc=tony@atomide.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