From: Viresh Kumar <viresh.kumar@linaro.org>
To: Stephan Gerhold <stephan@gerhold.net>
Cc: "Rafael J. Wysocki" <rjw@rjwysocki.net>,
Kevin Hilman <khilman@kernel.org>,
Ulf Hansson <ulf.hansson@linaro.org>, Nishanth Menon <nm@ti.com>,
Stephen Boyd <sboyd@kernel.org>,
linux-pm@vger.kernel.org, linux-kernel@vger.kernel.org,
Niklas Cassel <nks@flawful.org>
Subject: Re: [RFC PATCH 2/3] opp: Set required OPPs in reverse order when scaling down
Date: Mon, 24 Aug 2020 17:00:27 +0530 [thread overview]
Message-ID: <20200824113027.lzh6fp4bottjl6cc@vireshk-i7> (raw)
In-Reply-To: <20200821163152.GA3422@gerhold.net>
On 21-08-20, 18:31, Stephan Gerhold wrote:
> This patch does not apply anymore after the cleanup you pushed to
> opp/linux-next. I would be happy to send a v2 with that fixed.
>
> On my other OPP patch set you mentioned that you might apply these
> directly with some of your own changes - would you also prefer to do it
> yourself in this case or should I send a v2?
I will pick the first 2 myself, that's fine. Lets see where we go with
the third one :)
> Still looking for your feedback on both patch sets by the way! :)
Sorry about the delay, I was on vacation for over a week in between and
this and the other patchset was a bit tricky (which you may have not
realized, not sure, as I wondered if something will not work within
the OPP core for v1 binding, but it did finally I believe) :)
--
viresh
next prev parent reply other threads:[~2020-08-24 11:35 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-30 8:01 [RFC PATCH 0/3] opp: required_opps: Power on genpd, scale down in reverse order Stephan Gerhold
2020-07-30 8:01 ` [RFC PATCH 1/3] opp: Reduce code duplication in _set_required_opps() Stephan Gerhold
2020-08-24 11:18 ` Viresh Kumar
2020-08-24 11:30 ` Stephan Gerhold
2020-08-24 12:10 ` Viresh Kumar
2020-08-24 12:23 ` Stephan Gerhold
2020-07-30 8:01 ` [RFC PATCH 2/3] opp: Set required OPPs in reverse order when scaling down Stephan Gerhold
2020-08-21 16:31 ` Stephan Gerhold
2020-08-24 11:30 ` Viresh Kumar [this message]
2020-08-24 11:42 ` Stephan Gerhold
2020-07-30 8:01 ` [RFC PATCH 3/3] opp: Power on (virtual) power domains managed by the OPP core Stephan Gerhold
2020-08-24 11:27 ` Viresh Kumar
2020-08-24 11:55 ` Stephan Gerhold
2020-08-24 14:36 ` Ulf Hansson
2020-08-24 15:08 ` Stephan Gerhold
2020-08-25 4:43 ` Viresh Kumar
2020-08-25 6:43 ` Ulf Hansson
2020-08-25 7:33 ` Stephan Gerhold
2020-08-25 12:42 ` Ulf Hansson
2020-08-26 8:31 ` Stephan Gerhold
2020-08-12 8:53 ` [RFC PATCH 0/3] opp: required_opps: Power on genpd, scale down in reverse order Ulf Hansson
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=20200824113027.lzh6fp4bottjl6cc@vireshk-i7 \
--to=viresh.kumar@linaro.org \
--cc=khilman@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=nks@flawful.org \
--cc=nm@ti.com \
--cc=rjw@rjwysocki.net \
--cc=sboyd@kernel.org \
--cc=stephan@gerhold.net \
--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 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).