From: Stephen Boyd <sboyd@codeaurora.org>
To: Rajendra Nayak <rnayak@codeaurora.org>
Cc: Mike Turquette <mturquette@baylibre.com>,
linux-kernel@vger.kernel.org, linux-clk@vger.kernel.org,
Rob Clark <robdclark@gmail.com>,
"Rafael J . Wysocki" <rjw@rjwysocki.net>,
Kevin Hilman <khilman@kernel.org>,
linux-pm@vger.kernel.org, linux-arm-msm@vger.kernel.org,
Ulf Hansson <ulf.hansson@linaro.org>
Subject: Re: [PATCH v2 2/2] clk: qcom: Make oxili GDSC parent of oxili_cx GDSC
Date: Thu, 12 Nov 2015 22:14:09 -0800 [thread overview]
Message-ID: <20151113061409.GI15032@codeaurora.org> (raw)
In-Reply-To: <564564CA.5040608@codeaurora.org>
On 11/13, Rajendra Nayak wrote:
>
> On 10/07/2015 01:02 AM, Stephen Boyd wrote:
> > On 10/01, Stephen Boyd wrote:
> >> The oxili_cx GDSC is inside the power domain of the oxili GDSC.
> >> Add the dependency so that the CX domain can properly power up.
> >>
> >> Reported-by: Rob Clark <robdclark@gmail.com>
> >> Cc: Rajendra Nayak <rnayak@codeaurora.org>
> >> Signed-off-by: Stephen Boyd <sboyd@codeaurora.org>
> >> ---
> >
> > Applied to clk-next
>
> I don't see this in clk-next. Was this dropped for some reason?
>
Hm.. It's merged into Linus' tree now
b68f2c3b882202aba97a488c1fede0e99f7261e2
unless I missed something.
--
Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum,
a Linux Foundation Collaborative Project
next prev parent reply other threads:[~2015-11-13 6:14 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-01 19:22 [PATCH v2 0/2] Make oxili GDSC parent of oxili_cx GDSC Stephen Boyd
2015-10-01 19:22 ` [PATCH v2 1/2] PM / Domains: Make pm_genpd_{add,remove}_subdomain() available to modules Stephen Boyd
2015-10-05 20:55 ` Rafael J. Wysocki
2015-10-06 19:32 ` Stephen Boyd
2015-10-01 19:22 ` [PATCH v2 2/2] clk: qcom: Make oxili GDSC parent of oxili_cx GDSC Stephen Boyd
2015-10-06 19:32 ` Stephen Boyd
2015-11-13 4:19 ` Rajendra Nayak
2015-11-13 6:14 ` Stephen Boyd [this message]
2015-11-13 6:28 ` Rajendra Nayak
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=20151113061409.GI15032@codeaurora.org \
--to=sboyd@codeaurora.org \
--cc=khilman@kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=mturquette@baylibre.com \
--cc=rjw@rjwysocki.net \
--cc=rnayak@codeaurora.org \
--cc=robdclark@gmail.com \
--cc=ulf.hansson@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.