From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Todd Fischer <todd.fischer@ridgerun.com>
Cc: linux-kernel@vger.kernel.org,
davinci-linux-open-source@linux.davincidsp.com,
sameo@linux.intel.com, lrg@slimlogic.co.uk
Subject: Re: [PATCH 3/4]-V2 Cleaned up name space so each MFD sub-driver uses a different name space.
Date: Mon, 5 Apr 2010 14:49:13 +0100 [thread overview]
Message-ID: <20100405134913.GH6580@rakim.wolfsonmicro.main> (raw)
In-Reply-To: <1270244253-4234-4-git-send-email-todd.fischer@ridgerun.com>
On Fri, Apr 02, 2010 at 03:37:32PM -0600, Todd Fischer wrote:
> Move from using tps or tsp6507x to tps6057x_pmic in a consistent manner.
>
> Signed-off-by: Todd Fischer <todd.fischer@ridgerun.com>
Acked-by: Mark Brown <broonie@opensource.wolfsonicro.com>
next prev parent reply other threads:[~2010-04-05 13:49 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-02 21:37 [PATCH 0/4]-V2 TPS6507x MFD driver Todd Fischer
2010-04-02 21:37 ` [PATCH 1/4]-V2 Move TPS6507x register definition to header file Todd Fischer
2010-04-02 21:37 ` [PATCH 2/4]-V2 Make room for other tps6507x drivers to have board specific initialization data Todd Fischer
2010-04-02 21:37 ` [PATCH 3/4]-V2 Cleaned up name space so each MFD sub-driver uses a different name space Todd Fischer
2010-04-02 21:37 ` [PATCH 4/4]-V2 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-05 13:56 ` Mark Brown
2010-04-05 13:49 ` Mark Brown [this message]
2010-04-05 13:48 ` [PATCH 2/4]-V2 Make room for other tps6507x drivers to have board specific initialization data Mark Brown
2010-04-05 13:46 ` [PATCH 1/4]-V2 Move TPS6507x register definition to header file Mark Brown
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=20100405134913.GH6580@rakim.wolfsonmicro.main \
--to=broonie@opensource.wolfsonmicro.com \
--cc=davinci-linux-open-source@linux.davincidsp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lrg@slimlogic.co.uk \
--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