From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Paul Bolle <pebolle@tiscali.nl>
Cc: Stephen Warren <swarren@wwwdotorg.org>,
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: Mon, 8 Apr 2013 13:01:25 +0100 [thread overview]
Message-ID: <20130408120059.GF9243@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <1365416662.1830.86.camel@x61.thuisdomein>
[-- Attachment #1: Type: text/plain, Size: 918 bytes --]
On Mon, Apr 08, 2013 at 12:24:22PM +0200, Paul Bolle wrote:
> 0) This patch ended up as mainline commit
> bc8ce4afd7ee7e1421c935d24b1f879f82afdd4e, which is part of v3.9-rc6.
Numbering your paragraphs and using full commit IDs like this doesn't
help with legibility...
> 2) The following (draft) patch silences this warning. I'm a bit
> uncertain what the regmap_parse_*() functions are meant to do. So I'd
> like to first ask whether something along these lines is acceptable.
Nope, this breaks v3.9 - in that version they both modify in place and
return the parsed value. In v3.10 it already does what you have because
the in place and return value versions have been split.
We need to either revert the commit from v3.9 on the basis that nobody
noticed the issue until some other work so it can't be that bad or come
up with a more invasive fix, at this point in the cycle I'm more
inclined to do the latter.
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2013-04-08 12:01 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
2013-04-08 10:24 ` Paul Bolle
2013-04-08 12:01 ` Mark Brown [this message]
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=20130408120059.GF9243@opensource.wolfsonmicro.com \
--to=broonie@opensource.wolfsonmicro.com \
--cc=ldewangan@nvidia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=pebolle@tiscali.nl \
--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