From: Mark Brown <broonie@kernel.org>
To: Axel Lin <axel.lin@ingics.com>
Cc: Liam Girdwood <lgirdwood@gmail.com>,
linux-kernel@vger.kernel.org,
Laxman Dewangan <ldewangan@nvidia.com>
Subject: Re: [PATCH] regulator: max8973: Don't override control1 variable when set ramp delay bits
Date: Wed, 24 Apr 2013 10:53:18 +0100 [thread overview]
Message-ID: <20130424095318.GZ5019@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <1366733695.7020.1.camel@phoenix>
[-- Attachment #1: Type: text/plain, Size: 296 bytes --]
On Wed, Apr 24, 2013 at 12:14:55AM +0800, Axel Lin wrote:
> Current code overrides control1 variable when setting ramp delay bits.
> Fix it by just setting ramp_delay bits.
Applied, thanks. Laxman, please check your acks can be cut'n'pasted -
there's regularly things I need to fix up by hand.
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
prev parent reply other threads:[~2013-04-24 9:53 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-23 16:14 [PATCH] regulator: max8973: Don't override control1 variable when set ramp delay bits Axel Lin
2013-04-24 6:05 ` Laxman Dewangan
2013-04-24 9:53 ` Mark Brown [this message]
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=20130424095318.GZ5019@opensource.wolfsonmicro.com \
--to=broonie@kernel.org \
--cc=axel.lin@ingics.com \
--cc=ldewangan@nvidia.com \
--cc=lgirdwood@gmail.com \
--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