From: Samuel Ortiz <sameo@linux.intel.com>
To: Kevin Hilman <khilman@deeprootsystems.com>
Cc: Todd Fischer <todd.fischer@ridgerun.com>,
linux-kernel@vger.kernel.org,
davinci-linux-open-source@linux.davincidsp.com,
lrg@slimlogic.co.uk, broonie@opensource.wolfsonmicro.com
Subject: Re: [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.
Date: Sun, 9 May 2010 23:09:41 +0200 [thread overview]
Message-ID: <20100509210940.GA3269@sortiz.org> (raw)
In-Reply-To: <87633kacmq.fsf@deeprootsystems.com>
Hi Kevin,
On Wed, Apr 21, 2010 at 11:23:09AM -0700, Kevin Hilman wrote:
> Todd Fischer <todd.fischer@ridgerun.com> writes:
>
> > Add MFD driver for TPS6507x family of multi-function chips. Move TPS6507x
> > regulator driver from being stand-alone driver to using the MFD TPS6507x driver.
> >
> > Signed-off-by: Todd Fischer <todd.fischer@ridgerun.com>
>
> [...]
>
> Not sure whose tree this is queued in currently, but testing with
> current davinci git, I had a compile problem...
This is fixed in the MFD tree.
Cheers,
Samuel.
--
Intel Open Source Technology Centre
http://oss.intel.com/
next prev parent reply other threads:[~2010-05-09 21:09 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 [this message]
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
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=20100509210940.GA3269@sortiz.org \
--to=sameo@linux.intel.com \
--cc=broonie@opensource.wolfsonmicro.com \
--cc=davinci-linux-open-source@linux.davincidsp.com \
--cc=khilman@deeprootsystems.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lrg@slimlogic.co.uk \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.