From: Liam Girdwood <lrg@ti.com>
To: Mark Brown <broonie@opensource.wolfsonmicro.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] regulator: core: Fast path non-deferred disables
Date: Fri, 07 Sep 2012 16:03:09 +0100 [thread overview]
Message-ID: <1347030189.4625.0.camel@odin> (raw)
In-Reply-To: <1346986880-28846-1-git-send-email-broonie@opensource.wolfsonmicro.com>
On Fri, 2012-09-07 at 11:01 +0800, Mark Brown wrote:
> Users (especially framework code) may end up passing in a zero deferral
> time depending on runtime conditions or configuration. If they do then
> just call regulator_disable() directly to save scheduling.
>
> Signed-off-by: Mark Brown <broonie@opensource.wolfsonmicro.com>
Acked-by: Liam Girdwood <lrg@ti.com>
prev parent reply other threads:[~2012-09-07 15:03 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-07 3:01 [PATCH] regulator: core: Fast path non-deferred disables Mark Brown
2012-09-07 15:03 ` Liam Girdwood [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=1347030189.4625.0.camel@odin \
--to=lrg@ti.com \
--cc=broonie@opensource.wolfsonmicro.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;
as well as URLs for NNTP newsgroup(s).