From: Stephen Boyd <sboyd@codeaurora.org>
To: Thierry Reding <thierry.reding@gmail.com>
Cc: Viresh Kumar <viresh.kumar@linaro.org>,
Alexandre Courbot <gnurou@gmail.com>,
Stephen Warren <swarren@wwwdotorg.org>,
Mikko Perttunen <mikko.perttunen@kapsi.fi>,
Tuomas Tynkkynen <ttynkkynen@nvidia.com>,
Krzysztof Kozlowski <k.kozlowski@samsung.com>,
"Rafael J. Wysocki" <rafael.j.wysocki@intel.com>,
linux-pm@vger.kernel.org, linux-clk@vger.kernel.org,
linux-tegra@vger.kernel.org
Subject: Re: [PATCH] clk: tegra: dfll: Properly protect OPP list
Date: Mon, 14 Sep 2015 12:54:05 -0700 [thread overview]
Message-ID: <20150914195405.GB21561@codeaurora.org> (raw)
In-Reply-To: <20150911113531.GA16323@ulmo>
On 09/11, Thierry Reding wrote:
> On Fri, Sep 11, 2015 at 08:05:27AM +0530, Viresh Kumar wrote:
> > On 10-09-15, 10:51, Stephen Boyd wrote:
> > > Don't we already have an rcu_read_lock() at the beginning of this
> > > function? I don't understand why we need to nest them in the same
> > > function.
> >
> > +1
>
> My bad, I wasn't looking closely enough. The second hunk can be dropped.
>
Ok. I applied the first hunk to clk-fixes.
--
Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum,
a Linux Foundation Collaborative Project
prev parent reply other threads:[~2015-09-14 19:54 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-10 13:55 [PATCH] clk: tegra: dfll: Properly protect OPP list Thierry Reding
2015-09-10 17:51 ` Stephen Boyd
[not found] ` <20150910175144.GB15099-sgV2jX0FEOL9JmXXK+q4OQ@public.gmane.org>
2015-09-11 2:35 ` Viresh Kumar
2015-09-11 11:35 ` Thierry Reding
2015-09-14 19:54 ` Stephen Boyd [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=20150914195405.GB21561@codeaurora.org \
--to=sboyd@codeaurora.org \
--cc=gnurou@gmail.com \
--cc=k.kozlowski@samsung.com \
--cc=linux-clk@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=mikko.perttunen@kapsi.fi \
--cc=rafael.j.wysocki@intel.com \
--cc=swarren@wwwdotorg.org \
--cc=thierry.reding@gmail.com \
--cc=ttynkkynen@nvidia.com \
--cc=viresh.kumar@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 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).