From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Shawn Guo <shawn.guo@linaro.org>
Cc: cpufreq@vger.kernel.org, linux-pm@vger.kernel.org,
"Rafael J. Wysocki" <rjw@sisk.pl>, Kevin Hilman <khilman@ti.com>,
Nishanth Menon <nm@ti.com>,
Shilimkar Santosh <santosh.shilimkar@ti.com>,
Richard Zhao <richard.zhao@freescale.com>,
Russell King - ARM Linux <linux@arm.linux.org.uk>,
Mike Turquette <mturquette@linaro.org>,
devicetree-discuss@lists.ozlabs.org,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v2 3/4] regulator: add a new API regulator_set_voltage_tol()
Date: Thu, 9 Aug 2012 11:53:50 +0100 [thread overview]
Message-ID: <20120809105349.GL24328@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <20120808143004.GB14718@S2101-09.ap.freescale.net>
On Wed, Aug 08, 2012 at 10:30:07PM +0800, Shawn Guo wrote:
> On Wed, Aug 08, 2012 at 02:35:40PM +0100, Mark Brown wrote:
> > Applied, thanks! It's on a separate branch so can easily be either
> > applied somewhere else or merged into another tree if required for
> > dependencies, just let me know.
> I intended to have the whole series go via cpufreq tree with your ack
> on this patch. But I could also ask Rafael to merge your branch to
> resolve the dependency.
I anticipate wanting the new API in other trees too (I have one likely
use in mind) so having it only in the cpufreq tree would be inconvenient.
The whole reason to have this in the regulator API is that it's
something that's useful outside your cpufreq code!
WARNING: multiple messages have this Message-ID (diff)
From: broonie@opensource.wolfsonmicro.com (Mark Brown)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2 3/4] regulator: add a new API regulator_set_voltage_tol()
Date: Thu, 9 Aug 2012 11:53:50 +0100 [thread overview]
Message-ID: <20120809105349.GL24328@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <20120808143004.GB14718@S2101-09.ap.freescale.net>
On Wed, Aug 08, 2012 at 10:30:07PM +0800, Shawn Guo wrote:
> On Wed, Aug 08, 2012 at 02:35:40PM +0100, Mark Brown wrote:
> > Applied, thanks! It's on a separate branch so can easily be either
> > applied somewhere else or merged into another tree if required for
> > dependencies, just let me know.
> I intended to have the whole series go via cpufreq tree with your ack
> on this patch. But I could also ask Rafael to merge your branch to
> resolve the dependency.
I anticipate wanting the new API in other trees too (I have one likely
use in mind) so having it only in the cpufreq tree would be inconvenient.
The whole reason to have this in the regulator API is that it's
something that's useful outside your cpufreq code!
next prev parent reply other threads:[~2012-08-09 10:53 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-05 15:05 [PATCH v2 0/4] Add a generic cpufreq-cpu0 driver Shawn Guo
2012-08-05 15:05 ` Shawn Guo
[not found] ` <1344179121-17738-1-git-send-email-shawn.guo-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org>
2012-08-05 15:05 ` [PATCH v2 1/4] ARM: add cpufreq transiton notifier to adjust loops_per_jiffy for smp Shawn Guo
2012-08-05 15:05 ` Shawn Guo
2012-08-05 15:05 ` [PATCH v2 2/4] PM / OPP: Initialize OPP table from device tree Shawn Guo
2012-08-05 15:05 ` Shawn Guo
[not found] ` <1344179121-17738-3-git-send-email-shawn.guo-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org>
2012-08-06 2:50 ` Rob Herring
2012-08-06 2:50 ` Rob Herring
2012-08-06 3:19 ` Shawn Guo
2012-08-06 3:19 ` Shawn Guo
2012-08-06 4:43 ` Rob Herring
2012-08-06 4:43 ` Rob Herring
2012-08-06 5:23 ` Shawn Guo
2012-08-06 5:23 ` Shawn Guo
2012-08-05 15:05 ` [PATCH v2 3/4] regulator: add a new API regulator_set_voltage_tol() Shawn Guo
2012-08-05 15:05 ` Shawn Guo
2012-08-08 13:35 ` Mark Brown
2012-08-08 13:35 ` Mark Brown
2012-08-08 14:30 ` Shawn Guo
2012-08-08 14:30 ` Shawn Guo
2012-08-09 10:53 ` Mark Brown [this message]
2012-08-09 10:53 ` Mark Brown
2012-08-05 15:05 ` [PATCH v2 4/4] cpufreq: Add a generic cpufreq-cpu0 driver Shawn Guo
2012-08-05 15:05 ` Shawn Guo
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=20120809105349.GL24328@opensource.wolfsonmicro.com \
--to=broonie@opensource.wolfsonmicro.com \
--cc=cpufreq@vger.kernel.org \
--cc=devicetree-discuss@lists.ozlabs.org \
--cc=khilman@ti.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-pm@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
--cc=mturquette@linaro.org \
--cc=nm@ti.com \
--cc=richard.zhao@freescale.com \
--cc=rjw@sisk.pl \
--cc=santosh.shilimkar@ti.com \
--cc=shawn.guo@linaro.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.