From: Viresh Kumar <viresh.kumar@linaro.org>
To: Leonard Crestez <leonard.crestez@nxp.com>
Cc: "Saravana Kannan" <saravanak@google.com>,
"Rafael J. Wysocki" <rjw@rjwysocki.net>,
"Stephen Boyd" <sboyd@kernel.org>,
"Artur Świgoń" <a.swigon@partner.samsung.com>,
"Krzysztof Kozlowski" <krzk@kernel.org>,
"Georgi Djakov" <georgi.djakov@linaro.org>,
"Chanwoo Choi" <cw00.choi@samsung.com>,
"MyungJoo Ham" <myungjoo.ham@samsung.com>,
"Kyungmin Park" <kyungmin.park@samsung.com>,
"Alexandre Bailon" <abailon@baylibre.com>,
"linux-pm@vger.kernel.org" <linux-pm@vger.kernel.org>
Subject: Re: [RFC 0/4] opp: Parse required-opp as dev_pm_qos_request
Date: Wed, 21 Aug 2019 10:48:22 +0530 [thread overview]
Message-ID: <20190821051822.pmfnoamqmpr42ldb@vireshk-i7> (raw)
In-Reply-To: <VI1PR04MB7023B5D1305A4A4BB9DF534FEEAB0@VI1PR04MB7023.eurprd04.prod.outlook.com>
On 20-08-19, 15:48, Leonard Crestez wrote:
> The interconnect subsystem has additional capabilities (scaling along a
> path) so I plan to use that instead. You can treat this series as a
> "curiosity".
So I can just ignore it ;)
--
viresh
prev parent reply other threads:[~2019-08-21 5:18 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-06 11:12 [RFC 0/4] opp: Parse required-opp as dev_pm_qos_request Leonard Crestez
2019-08-06 11:12 ` [RFC 1/4] opp: Drop const from opp_device struct device Leonard Crestez
2019-08-06 11:12 ` [RFC 2/4] opp: Add dev_pm_opp_table_get_device Leonard Crestez
2019-08-06 11:12 ` [RFC 3/4] opp: Add dev_pm_parse_required_opp_as_qos Leonard Crestez
2019-08-06 11:12 ` [RFC 4/4] PM / QoS: Add dev_pm_qos_get_curr_value Leonard Crestez
2019-08-20 6:52 ` [RFC 0/4] opp: Parse required-opp as dev_pm_qos_request Viresh Kumar
2019-08-20 9:02 ` Leonard Crestez
2019-08-20 9:22 ` Viresh Kumar
2019-08-20 15:48 ` Leonard Crestez
2019-08-21 5:18 ` Viresh Kumar [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=20190821051822.pmfnoamqmpr42ldb@vireshk-i7 \
--to=viresh.kumar@linaro.org \
--cc=a.swigon@partner.samsung.com \
--cc=abailon@baylibre.com \
--cc=cw00.choi@samsung.com \
--cc=georgi.djakov@linaro.org \
--cc=krzk@kernel.org \
--cc=kyungmin.park@samsung.com \
--cc=leonard.crestez@nxp.com \
--cc=linux-pm@vger.kernel.org \
--cc=myungjoo.ham@samsung.com \
--cc=rjw@rjwysocki.net \
--cc=saravanak@google.com \
--cc=sboyd@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).