From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Stephen Warren <swarren@wwwdotorg.org>
Cc: linux-kernel@vger.kernel.org, Stephen Warren <swarren@nvidia.com>,
Laxman Dewangan <ldewangan@nvidia.com>
Subject: Re: [PATCH] regmap: don't corrupt work buffer in _regmap_raw_write()
Date: Thu, 21 Mar 2013 20:09:39 +0100 [thread overview]
Message-ID: <20130321190939.GI15926@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <1363820522-25954-1-git-send-email-swarren@wwwdotorg.org>
[-- Attachment #1: Type: text/plain, Size: 356 bytes --]
On Wed, Mar 20, 2013 at 05:02:02PM -0600, Stephen Warren wrote:
> From: Stephen Warren <swarren@nvidia.com>
>
> _regmap_raw_write() contains code to call regcache_write() to write
> values to the cache. That code calls memcpy() to copy the value data to
> the start of the work_buf. However, at least when _regmap_raw_write() is
Applied, thanks.
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2013-03-21 19:09 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-20 23:02 [PATCH] regmap: don't corrupt work buffer in _regmap_raw_write() Stephen Warren
2013-03-21 19:09 ` Mark Brown [this message]
2013-04-08 10:24 ` Paul Bolle
2013-04-08 12:01 ` Mark Brown
2013-04-08 16:42 ` Stephen Warren
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=20130321190939.GI15926@opensource.wolfsonmicro.com \
--to=broonie@opensource.wolfsonmicro.com \
--cc=ldewangan@nvidia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=swarren@nvidia.com \
--cc=swarren@wwwdotorg.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