From: Lee Jones <lee.jones@linaro.org>
To: Mark Brown <broonie@kernel.org>
Cc: Samuel Ortiz <sameo@linux.intel.com>,
alsa-devel@alsa-project.org, linux-kernel@vger.kernel.org,
linaro-kernel@lists.linaro.org, Mark Brown <broonie@linaro.org>
Subject: Re: [PATCH 1/3] mfd: mc13xxx: Don't require lock for simple register I/O
Date: Wed, 25 Sep 2013 12:19:03 +0100 [thread overview]
Message-ID: <20130925111903.GF5132@lee--X1> (raw)
In-Reply-To: <1379960073-23245-1-git-send-email-broonie@kernel.org>
On Mon, 23 Sep 2013, Mark Brown wrote:
> From: Mark Brown <broonie@linaro.org>
>
> Since the conversion to regmap there has been no need for device level
> locking for I/O as regmap provides locking so remove the locks.
>
> Signed-off-by: Mark Brown <broonie@linaro.org>
> ---
> drivers/mfd/mc13xxx-core.c | 5 -----
> 1 file changed, 5 deletions(-)
Applied, thanks.
--
Lee Jones
Linaro STMicroelectronics Landing Team Lead
Linaro.org │ Open source software for ARM SoCs
Follow Linaro: Facebook | Twitter | Blog
next prev parent reply other threads:[~2013-09-25 11:19 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-23 18:14 [PATCH 1/3] mfd: mc13xxx: Don't require lock for simple register I/O Mark Brown
2013-09-23 18:14 ` [PATCH 2/3] mfd: mc13xxx: Move SPI erratum workaround into SPI I/O function Mark Brown
2013-09-25 11:19 ` Lee Jones
2013-09-25 11:31 ` Mark Brown
2013-09-25 11:46 ` Lee Jones
2013-09-25 11:55 ` Lee Jones
2013-09-25 12:35 ` Mark Brown
2013-09-25 12:51 ` Lee Jones
2013-09-25 12:55 ` Mark Brown
2013-09-25 13:05 ` Lee Jones
2013-09-23 18:14 ` [PATCH 3/3] ASoC: mc13783: Use regmap directly from ASoC Mark Brown
2013-09-25 11:19 ` Lee Jones [this message]
-- strict thread matches above, loose matches on Subject: below --
2013-09-18 18:06 [PATCH 1/3] mfd: mc13xxx: Don't require lock for simple register I/O 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=20130925111903.GF5132@lee--X1 \
--to=lee.jones@linaro.org \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@kernel.org \
--cc=broonie@linaro.org \
--cc=linaro-kernel@lists.linaro.org \
--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;
as well as URLs for NNTP newsgroup(s).