From: Viresh Kumar <viresh.kumar@linaro.org>
To: "Rafael J. Wysocki" <rafael@kernel.org>
Cc: Rafael Wysocki <rjw@rjwysocki.net>,
Linux PM <linux-pm@vger.kernel.org>,
Vincent Guittot <vincent.guittot@linaro.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH V2 04/10] cpufreq: powerpc_cbe: Switch to QoS requests instead of cpufreq notifier
Date: Mon, 19 Aug 2019 07:56:14 +0530 [thread overview]
Message-ID: <20190819022614.oy5qdozde2afibwu@vireshk-i7> (raw)
In-Reply-To: <CAJZ5v0gQ2RCZGo03=7DoUAxw86wSEaXdnJ2KtknU3uUtXCqmvQ@mail.gmail.com>
On 09-08-19, 11:01, Rafael J. Wysocki wrote:
> On Fri, Aug 9, 2019 at 4:34 AM Viresh Kumar <viresh.kumar@linaro.org> wrote:
> >
> > On 23-07-19, 11:44, Viresh Kumar wrote:
> > > The cpufreq core now takes the min/max frequency constraints via QoS
> > > requests and the CPUFREQ_ADJUST notifier shall get removed later on.
> > >
> > > Switch over to using the QoS request for maximum frequency constraint
> > > for ppc_cbe_cpufreq driver.
> > >
> > > Signed-off-by: Viresh Kumar <viresh.kumar@linaro.org>
> > > ---
> > > drivers/cpufreq/ppc_cbe_cpufreq.c | 19 +++++-
> > > drivers/cpufreq/ppc_cbe_cpufreq.h | 8 +++
> > > drivers/cpufreq/ppc_cbe_cpufreq_pmi.c | 96 +++++++++++++++++----------
> > > 3 files changed, 86 insertions(+), 37 deletions(-)
> >
> > -------------------------8<-------------------------
>
> If you do it this way, Patchwork will not pick up the patch.
>
> Please send afresh with "[Update]" or bumped up version number in the
> subject (or both).
Okay, will take care of this in future. Was away on holidays and so
the late reply. Thanks.
--
viresh
next prev parent reply other threads:[~2019-08-19 2:26 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-23 6:14 [PATCH V2 00/10] cpufreq: Migrate users of policy notifiers to QoS requests Viresh Kumar
2019-07-23 6:14 ` [PATCH V2 01/10] cpufreq: Add policy create/remove notifiers Viresh Kumar
2019-07-23 6:14 ` [PATCH V2 02/10] thermal: cpu_cooling: Switch to QoS requests instead of cpufreq notifier Viresh Kumar
2019-07-23 6:14 ` [PATCH V2 03/10] powerpc: macintosh: " Viresh Kumar
2019-07-23 6:14 ` [PATCH V2 04/10] cpufreq: powerpc_cbe: " Viresh Kumar
2019-08-09 2:34 ` Viresh Kumar
2019-08-09 9:01 ` Rafael J. Wysocki
2019-08-19 2:26 ` Viresh Kumar [this message]
2019-08-19 6:42 ` Rafael J. Wysocki
2019-08-19 6:47 ` Viresh Kumar
2019-08-10 12:19 ` Rafael J. Wysocki
2019-07-23 6:14 ` [PATCH V2 05/10] ACPI: cpufreq: " Viresh Kumar
2019-08-05 9:42 ` Rafael J. Wysocki
2019-08-06 4:39 ` Viresh Kumar
2019-08-06 8:01 ` Rafael J. Wysocki
2019-08-06 8:47 ` Viresh Kumar
2019-08-09 2:33 ` Viresh Kumar
2019-08-10 12:13 ` Rafael J. Wysocki
2019-08-28 8:50 ` [PATCH V3 " Viresh Kumar
2019-07-23 6:14 ` [PATCH V2 06/10] arch_topology: Use CPUFREQ_CREATE_POLICY instead of CPUFREQ_NOTIFY Viresh Kumar
2019-07-25 13:36 ` Greg Kroah-Hartman
2019-07-23 6:14 ` [PATCH V2 07/10] video: sa1100fb: Remove cpufreq policy notifier Viresh Kumar
2019-07-23 6:14 ` [PATCH V2 08/10] video: pxafb: " Viresh Kumar
2019-07-23 6:14 ` [PATCH V2 09/10] cpufreq: Remove CPUFREQ_ADJUST and CPUFREQ_NOTIFY policy notifier events Viresh Kumar
2019-07-23 6:14 ` [PATCH V2 10/10] Documentation: cpufreq: Update policy notifier documentation Viresh Kumar
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=20190819022614.oy5qdozde2afibwu@vireshk-i7 \
--to=viresh.kumar@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=rafael@kernel.org \
--cc=rjw@rjwysocki.net \
--cc=vincent.guittot@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).