From: Samuel Ortiz <sameo@linux.intel.com>
To: Mark Brown <broonie@kernel.org>
Cc: Kukjin Kim <kgene.kim@samsung.com>,
Sangbeom Kim <sbkim73@samsung.com>,
Lee Jones <lee.jones@linaro.org>,
linux-kernel@vger.kernel.org, Mark Brown <broonie@linaro.org>
Subject: Re: [PATCH] mfd: sec: Provide max_register to regmap
Date: Tue, 2 Jul 2013 00:56:05 +0200 [thread overview]
Message-ID: <20130701225605.GD4572@zurbaran> (raw)
In-Reply-To: <1372716139-5586-1-git-send-email-broonie@kernel.org>
Hi Mark,
On Mon, Jul 01, 2013 at 11:02:19PM +0100, Mark Brown wrote:
> From: Mark Brown <broonie@linaro.org>
>
> Enable debugfs register dumps and greater error checking within the
> regmap API providing the maximum register to the regmap API.
>
> Signed-off-by: Mark Brown <broonie@linaro.org>
> ---
> drivers/mfd/sec-core.c | 41 ++++++++++++++++++++++++++++++++++++++++-
> 1 file changed, 40 insertions(+), 1 deletion(-)
Applied as well, thanks.
Cheers,
Samuel.
--
Intel Open Source Technology Centre
http://oss.intel.com/
prev parent reply other threads:[~2013-07-01 23:01 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-01 22:02 [PATCH] mfd: sec: Provide max_register to regmap Mark Brown
2013-07-01 22:56 ` 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=20130701225605.GD4572@zurbaran \
--to=sameo@linux.intel.com \
--cc=broonie@kernel.org \
--cc=broonie@linaro.org \
--cc=kgene.kim@samsung.com \
--cc=lee.jones@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sbkim73@samsung.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