From: Samuel Ortiz <sameo@linux.intel.com>
To: Mark Brown <broonie@opensource.wolfsonmicro.com>
Cc: linux-kernel@vger.kernel.org, patches@opensource.wolfsonmicro.com
Subject: Re: [PATCH] mfd: arizona: Provide platform data for MICBIAS configuration
Date: Sun, 3 Feb 2013 18:01:10 +0100 [thread overview]
Message-ID: <20130203170110.GJ8476@sortiz-mobl> (raw)
In-Reply-To: <1359391658-13479-1-git-send-email-broonie@opensource.wolfsonmicro.com>
Hi Mark,
On Tue, Jan 29, 2013 at 12:47:37AM +0800, Mark Brown wrote:
> Allow the MICBIAS voltages and other attributes to be configured by the
> platform.
>
> Signed-off-by: Mark Brown <broonie@opensource.wolfsonmicro.com>
> ---
> drivers/mfd/arizona-core.c | 23 +++++++++++++++++++++++
> include/linux/mfd/arizona/pdata.h | 12 ++++++++++++
> 2 files changed, 35 insertions(+)
Applied as well. After this one, I shouldn't have any pending patches from
you.
Cheers,
Samuel.
--
Intel Open Source Technology Centre
http://oss.intel.com/
prev parent reply other threads:[~2013-02-03 17:01 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-28 16:47 [PATCH] mfd: arizona: Provide platform data for MICBIAS configuration Mark Brown
2013-02-03 17:01 ` Samuel Ortiz [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=20130203170110.GJ8476@sortiz-mobl \
--to=sameo@linux.intel.com \
--cc=broonie@opensource.wolfsonmicro.com \
--cc=linux-kernel@vger.kernel.org \
--cc=patches@opensource.wolfsonmicro.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;
as well as URLs for NNTP newsgroup(s).