From: Liam Girdwood <lrg@slimlogic.co.uk>
To: Samuel Ortiz <sameo@linux.intel.com>
Cc: Todd Fischer <todd.fischer@ridgerun.com>,
linux-kernel@vger.kernel.org,
davinci-linux-open-source@linux.davincidsp.com,
Mark Brown <broonie@opensource.wolfsonmicro.com>
Subject: Re: [PATCH 0/4]-V3 TPS6507x MFD driver
Date: Tue, 06 Apr 2010 12:05:59 +0100 [thread overview]
Message-ID: <1270551959.3229.22.camel@odin> (raw)
In-Reply-To: <20100406105132.GC2688@rakim.wolfsonmicro.main>
Hi Samuel,
Please feel free to upstream via MFD.
On Tue, 2010-04-06 at 11:51 +0100, Mark Brown wrote:
> On Mon, Apr 05, 2010 at 08:23:55PM -0600, Todd Fischer wrote:
>
> > This is the third posting of the TPS6507x driver set. I have
> > resolved the concurrent access issue identified by Mark Brown.
> > Instead of using a mutex, I used the i2c_transfer() as done in
> > the similar routine in the wm8400-core.c file.
>
> All
>
> Acked-by: Mark Brown <broonie@opensource.wolfsonmicro.com>
Signed-off-by: Liam Girdwood <lrg@slimlogic.co.uk>
--
Freelance Developer, SlimLogic Ltd
ASoC and Voltage Regulator Maintainer.
http://www.slimlogic.co.uk
next prev parent reply other threads:[~2010-04-06 11:06 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-06 2:23 [PATCH 0/4]-V3 TPS6507x MFD driver Todd Fischer
2010-04-06 2:23 ` [PATCH 1/4]-V3 Move TPS6507x register definition to header file Todd Fischer
2010-04-06 2:23 ` [PATCH 2/4]-V3 Make room for other tps6507x drivers to have board specific initialization data Todd Fischer
2010-04-06 2:23 ` [PATCH 3/4]-V3 Cleaned up name space so each MFD sub-driver uses a different name space Todd Fischer
2010-04-06 2:23 ` [PATCH 4/4]-V3 Add MFD driver for TPS6507x family of multi-function chips and move TPS6507x regulator driver from being stand-alone to using the MFD driver Todd Fischer
2010-04-21 18:23 ` Kevin Hilman
2010-05-09 21:09 ` Samuel Ortiz
2010-05-10 14:18 ` Kevin Hilman
2010-04-06 10:51 ` [PATCH 0/4]-V3 TPS6507x " Mark Brown
2010-04-06 11:05 ` Liam Girdwood [this message]
2010-04-07 8:43 ` Samuel Ortiz
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=1270551959.3229.22.camel@odin \
--to=lrg@slimlogic.co.uk \
--cc=broonie@opensource.wolfsonmicro.com \
--cc=davinci-linux-open-source@linux.davincidsp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=sameo@linux.intel.com \
--cc=todd.fischer@ridgerun.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