From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Andres Salomon <dilinger@queued.net>
Cc: Samuel Ortiz <sameo@linux.intel.com>, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/17] mfd sharing support (v2, part 1)
Date: Mon, 14 Feb 2011 16:31:39 +0000 [thread overview]
Message-ID: <20110214163139.GE8226@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <20110211175735.0d4258dc@queued.net>
On Fri, Feb 11, 2011 at 05:57:35PM -0800, Andres Salomon wrote:
> Here's my second attempt[0] of the MFD sharing. Rather than go
> through with the whole thing, this is just the part which makes
> mfd_cells always available to MFD clients. I'm planning to later
> remove driver_data, and just use a (renamed) platform_data as a
> general cleanup, but for now.. Here's the first part.
Reviewed-by: Mark Brown <broonie@opensource.wolfsonmicro.com>
though I didn't go and check for existing platform data users in the
affected drivers.
prev parent reply other threads:[~2011-02-14 16:31 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-12 1:57 [PATCH 0/17] mfd sharing support (v2, part 1) Andres Salomon
2011-02-14 16:31 ` Mark Brown [this message]
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=20110214163139.GE8226@opensource.wolfsonmicro.com \
--to=broonie@opensource.wolfsonmicro.com \
--cc=dilinger@queued.net \
--cc=linux-kernel@vger.kernel.org \
--cc=sameo@linux.intel.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