From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Lars-Peter Clausen <lars@metafoo.de>
Cc: Dimitris Papastamos <dp@opensource.wolfsonmicro.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 2/2] regmap: Drop check whether a register is readable in regcache_read
Date: Thu, 17 Nov 2011 16:51:54 +0000 [thread overview]
Message-ID: <20111117165153.GB9008@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <1321472044-15686-2-git-send-email-lars@metafoo.de>
On Wed, Nov 16, 2011 at 08:34:04PM +0100, Lars-Peter Clausen wrote:
> One of the reasons for using a cache is to have a software shadow of a register
> which is writable but not readable. This allows us to do a read-modify-write
> operation on such a register.
Applied, thanks.
next prev parent reply other threads:[~2011-11-17 16:51 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-16 19:34 [PATCH v2 1/2] regmap: Properly round cache_word_size Lars-Peter Clausen
2011-11-16 19:34 ` [PATCH v2 2/2] regmap: Drop check whether a register is readable in regcache_read Lars-Peter Clausen
2011-11-17 16:51 ` Mark Brown [this message]
2011-11-17 16:51 ` [PATCH v2 1/2] regmap: Properly round cache_word_size 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=20111117165153.GB9008@opensource.wolfsonmicro.com \
--to=broonie@opensource.wolfsonmicro.com \
--cc=dp@opensource.wolfsonmicro.com \
--cc=lars@metafoo.de \
--cc=linux-kernel@vger.kernel.org \
/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