From: Viresh Kumar <viresh.kumar@linaro.org>
To: Rafael Wysocki <rjw@rjwysocki.net>,
nm@ti.com, Stephen Boyd <sboyd@codeaurora.org>
Cc: linaro-kernel@lists.linaro.org, linux-pm@vger.kernel.org,
Bartlomiej Zolnierkiewicz <b.zolnierkie@samsung.com>,
Dmitry Torokhov <dtor@chromium.org>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Len Brown <len.brown@intel.com>,
open list <linux-kernel@vger.kernel.org>,
Pavel Machek <pavel@ucw.cz>, Shawn Guo <shawnguo@kernel.org>
Subject: Re: [PATCH V2 2/3] PM / OPP: Parse 'opp-supported-hw' binding
Date: Fri, 4 Dec 2015 13:53:39 +0530 [thread overview]
Message-ID: <20151204082339.GH3430@ubuntu> (raw)
In-Reply-To: <20151201065252.GD4459@ubuntu>
On 01-12-15, 12:22, Viresh Kumar wrote:
> Since these functions are *only* going to be called before any OPPs
> are added for the device, and hence ruling out any concurrent readers,
> maybe we can guarantee that with this:
@Rafael: Stephen has gone for vacations until end of year :(, can you
please help with some reviews ?
--
viresh
next prev parent reply other threads:[~2015-12-04 8:23 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <cover.1447904566.git.viresh.kumar@linaro.org>
2015-11-19 3:43 ` [PATCH V2 1/3] PM / OPP: Add missing doc comments Viresh Kumar
2015-11-23 23:14 ` Rafael J. Wysocki
2015-11-19 3:43 ` [PATCH V2 2/3] PM / OPP: Parse 'opp-supported-hw' binding Viresh Kumar
2015-11-25 20:51 ` Stephen Boyd
2015-11-27 4:45 ` Viresh Kumar
2015-12-01 6:52 ` Viresh Kumar
2015-12-04 8:23 ` Viresh Kumar [this message]
2015-12-08 15:01 ` Viresh Kumar
2015-12-08 16:50 ` Rafael J. Wysocki
2015-12-08 16:31 ` Viresh Kumar
2015-12-09 1:15 ` Rafael J. Wysocki
2015-12-09 2:34 ` Viresh Kumar
2015-12-09 22:06 ` Rafael J. Wysocki
2015-11-19 3:43 ` [PATCH V2 3/3] PM / OPP: Parse 'opp-<prop>-<name>' bindings Viresh Kumar
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=20151204082339.GH3430@ubuntu \
--to=viresh.kumar@linaro.org \
--cc=b.zolnierkie@samsung.com \
--cc=dtor@chromium.org \
--cc=gregkh@linuxfoundation.org \
--cc=len.brown@intel.com \
--cc=linaro-kernel@lists.linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=nm@ti.com \
--cc=pavel@ucw.cz \
--cc=rjw@rjwysocki.net \
--cc=sboyd@codeaurora.org \
--cc=shawnguo@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).