From: Viresh Kumar <viresh.kumar@linaro.org>
To: Nicola Mazzucato <nicola.mazzucato@arm.com>
Cc: linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org, linux-pm@vger.kernel.org,
sudeep.holla@arm.com, rjw@rjwysocki.net, vireshk@kernel.org,
cristian.marussi@arm.com, morten.rasmussen@arm.com,
chris.redpath@arm.com, ionela.voinescu@arm.com
Subject: Re: [PATCH v8 0/3] CPUFreq: Add support for opp-sharing cpus
Date: Fri, 19 Feb 2021 09:49:44 +0530 [thread overview]
Message-ID: <20210219041944.uox45mesrabvfm72@vireshk-i7> (raw)
In-Reply-To: <20210218222326.15788-1-nicola.mazzucato@arm.com>
On 18-02-21, 22:23, Nicola Mazzucato wrote:
> Hi Viresh,
>
> In this V8 I have addressed your comments:
> - correct the goto in patch 1/3
> - improve comment in patch 2/3 for dev_pm_opp_get_opp_count()
LGTM. I will apply them after the merge window is over. Thanks.
--
viresh
WARNING: multiple messages have this Message-ID (diff)
From: Viresh Kumar <viresh.kumar@linaro.org>
To: Nicola Mazzucato <nicola.mazzucato@arm.com>
Cc: linux-pm@vger.kernel.org, vireshk@kernel.org, rjw@rjwysocki.net,
linux-kernel@vger.kernel.org, cristian.marussi@arm.com,
sudeep.holla@arm.com, chris.redpath@arm.com,
ionela.voinescu@arm.com, morten.rasmussen@arm.com,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v8 0/3] CPUFreq: Add support for opp-sharing cpus
Date: Fri, 19 Feb 2021 09:49:44 +0530 [thread overview]
Message-ID: <20210219041944.uox45mesrabvfm72@vireshk-i7> (raw)
In-Reply-To: <20210218222326.15788-1-nicola.mazzucato@arm.com>
On 18-02-21, 22:23, Nicola Mazzucato wrote:
> Hi Viresh,
>
> In this V8 I have addressed your comments:
> - correct the goto in patch 1/3
> - improve comment in patch 2/3 for dev_pm_opp_get_opp_count()
LGTM. I will apply them after the merge window is over. Thanks.
--
viresh
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2021-02-19 4:20 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-18 22:23 [PATCH v8 0/3] CPUFreq: Add support for opp-sharing cpus Nicola Mazzucato
2021-02-18 22:23 ` Nicola Mazzucato
2021-02-18 22:23 ` [PATCH v8 1/3] scmi-cpufreq: Remove deferred probe Nicola Mazzucato
2021-02-18 22:23 ` Nicola Mazzucato
2021-02-18 22:23 ` [PATCH v8 2/3] scmi-cpufreq: Get opp_shared_cpus from opp-v2 for EM Nicola Mazzucato
2021-02-18 22:23 ` Nicola Mazzucato
2021-02-18 22:23 ` [PATCH v8 3/3] cpufreq: blacklist Arm Vexpress platforms in cpufreq-dt-platdev Nicola Mazzucato
2021-02-18 22:23 ` Nicola Mazzucato
2021-02-19 4:19 ` Viresh Kumar [this message]
2021-02-19 4:19 ` [PATCH v8 0/3] CPUFreq: Add support for opp-sharing cpus Viresh Kumar
2021-02-19 19:16 ` Sudeep Holla
2021-02-19 19:16 ` Sudeep Holla
2021-02-22 4:39 ` Viresh Kumar
2021-02-22 4:39 ` Viresh Kumar
2021-02-22 11:14 ` Sudeep Holla
2021-02-22 11:14 ` Sudeep Holla
2021-03-09 11:59 ` Sudeep Holla
2021-03-09 11:59 ` Sudeep Holla
2021-03-23 9:30 ` Sudeep Holla
2021-03-23 9:30 ` Sudeep Holla
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=20210219041944.uox45mesrabvfm72@vireshk-i7 \
--to=viresh.kumar@linaro.org \
--cc=chris.redpath@arm.com \
--cc=cristian.marussi@arm.com \
--cc=ionela.voinescu@arm.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=morten.rasmussen@arm.com \
--cc=nicola.mazzucato@arm.com \
--cc=rjw@rjwysocki.net \
--cc=sudeep.holla@arm.com \
--cc=vireshk@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 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.