From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: "Shilimkar, Santosh" <santosh.shilimkar@ti.com>
Cc: Felipe Balbi <felipe.balbi@nokia.com>,
"Krishnamoorthy, Balaji T" <balajitk@ti.com>,
"linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>,
"tony@atomide.com" <tony@atomide.com>,
"khilman@deeprootsystems.com" <khilman@deeprootsystems.com>,
"david-b@pacbell.net" <david-b@pacbell.net>,
"Nayak, Rajendra" <rnayak@ti.com>
Subject: Re: [RFC][PATCH 0/4] TWL6030 patch series
Date: Fri, 24 Jul 2009 10:20:34 +0100 [thread overview]
Message-ID: <20090724092034.GB27429@rakim.wolfsonmicro.main> (raw)
In-Reply-To: <EAF47CD23C76F840A9E7FCE10091EFAB02B59F2A0F@dbde02.ent.ti.com>
On Fri, Jul 24, 2009 at 09:46:27AM +0530, Shilimkar, Santosh wrote:
> Mark, Liam,
> Can you please your comments of regulator patches.
I'd really like to see the ifdefs go as someone else requested earlier
in the thread. Allowing both twl4030 and twl6030 support to be built
simultaneously is much nicer from a maintinance perspective and will
scale better as further devices are added to the family.
next prev parent reply other threads:[~2009-07-24 9:20 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-20 11:59 [RFC][PATCH 0/4] TWL6030 patch series Krishnamoorthy, Balaji T
2009-07-20 12:11 ` Felipe Balbi
2009-07-20 12:15 ` Mark Brown
2009-07-20 13:00 ` Krishnamoorthy, Balaji T
2009-07-24 4:16 ` Shilimkar, Santosh
2009-07-24 9:20 ` Mark Brown [this message]
2009-08-03 6:15 ` Shilimkar, Santosh
2009-08-03 14:25 ` Mark Brown
-- strict thread matches above, loose matches on Subject: below --
2009-07-20 13:34 Krishnamoorthy, Balaji T
2009-08-06 8:58 ` Krishnamoorthy, Balaji T
2009-08-11 13:00 ` Krishnamoorthy, Balaji T
2009-08-17 0:00 ` Samuel Ortiz
2009-08-17 5:16 ` Krishnamoorthy, Balaji T
2009-08-17 9:14 ` Samuel Ortiz
2009-08-17 9:42 ` Krishnamoorthy, Balaji T
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=20090724092034.GB27429@rakim.wolfsonmicro.main \
--to=broonie@opensource.wolfsonmicro.com \
--cc=balajitk@ti.com \
--cc=david-b@pacbell.net \
--cc=felipe.balbi@nokia.com \
--cc=khilman@deeprootsystems.com \
--cc=linux-omap@vger.kernel.org \
--cc=rnayak@ti.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