From: broonie@opensource.wolfsonmicro.com (Mark Brown)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2] regulator: max8649 Convert max8649 to use regmap api
Date: Mon, 24 Oct 2011 15:46:32 +0200 [thread overview]
Message-ID: <20111024134632.GC26033@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <1319462786-2602-1-git-send-email-jhbird.choi@gmail.com>
On Mon, Oct 24, 2011 at 10:26:26PM +0900, jhbird.choi at gmail.com wrote:
> From: Jonghwan Choi <jhbird.choi@gmail.com>
>
> Signed-off-by: Jonghwan Choi <jhbird.choi@gmail.com>
Looks good!
Acked-by: Mark Brown <broonie@opensource.wolfsonmicro.com>
Once the merge window is over it might be useful to look at enabling
register cache for the driver, you'll get a performance improvement as
it'll be able to skip the read part of read/modify/write cycles.
next prev parent reply other threads:[~2011-10-24 13:46 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-24 13:26 [PATCH v2] regulator: max8649 Convert max8649 to use regmap api jhbird.choi at gmail.com
2011-10-24 13:36 ` Haojian Zhuang
2011-10-24 13:46 ` Mark Brown [this message]
2011-10-31 21:44 ` Mark Brown
-- strict thread matches above, loose matches on Subject: below --
2011-10-21 8:57 jhbird.choi at samsung.com
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=20111024134632.GC26033@opensource.wolfsonmicro.com \
--to=broonie@opensource.wolfsonmicro.com \
--cc=linux-arm-kernel@lists.infradead.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;
as well as URLs for NNTP newsgroup(s).