From: "Rafael J. Wysocki" <rafael@kernel.org>
To: Viresh Kumar <viresh.kumar@linaro.org>
Cc: Peter Zijlstra <peterz@infradead.org>,
Rafael Wysocki <rjw@rjwysocki.net>,
Qian Cai <quic_qiancai@quicinc.com>,
Sudeep Holla <sudeep.holla@arm.com>,
Ingo Molnar <mingo@redhat.com>,
Juri Lelli <juri.lelli@redhat.com>,
Vincent Guittot <vincent.guittot@linaro.org>,
Dietmar Eggemann <dietmar.eggemann@arm.com>,
Steven Rostedt <rostedt@goodmis.org>,
Ben Segall <bsegall@google.com>, Mel Gorman <mgorman@suse.de>,
Daniel Bristot de Oliveira <bristot@redhat.com>,
Ionela Voinescu <ionela.voinescu@arm.com>,
Linux PM <linux-pm@vger.kernel.org>,
"Rafael J. Wysocki" <rafael@kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH V2] Revert "cpufreq: CPPC: Add support for frequency invariance"
Date: Fri, 11 Jun 2021 12:54:26 +0200 [thread overview]
Message-ID: <CAJZ5v0hQ_7cdTNiXuFtmwiiLXxZ1WzxmLrPA+Hp4Tp7i-qS4EQ@mail.gmail.com> (raw)
In-Reply-To: <20210611074008.57u27wtyqv4ossde@vireshk-i7>
On Fri, Jun 11, 2021 at 9:40 AM Viresh Kumar <viresh.kumar@linaro.org> wrote:
>
> On 11-06-21, 09:37, Peter Zijlstra wrote:
> > Alternatively: "depends on BROKEN" ?
>
> This is what I wanted to do, but Rafael didn't like it :)
>
> https://lore.kernel.org/linux-pm/28308fc0d38f252baf90e6ffb31fd2f8660be273.1623311808.git.viresh.kumar@linaro.org/
Right.
For new things I prefer to either fix them properly before the release
or revert and redo in a better way in the next cycle.
next prev parent reply other threads:[~2021-06-11 10:54 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-11 3:18 [PATCH V2] Revert "cpufreq: CPPC: Add support for frequency invariance" Viresh Kumar
2021-06-11 7:37 ` Peter Zijlstra
2021-06-11 7:40 ` Viresh Kumar
2021-06-11 10:54 ` Rafael J. Wysocki [this message]
2021-06-14 13:56 ` Rafael J. Wysocki
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=CAJZ5v0hQ_7cdTNiXuFtmwiiLXxZ1WzxmLrPA+Hp4Tp7i-qS4EQ@mail.gmail.com \
--to=rafael@kernel.org \
--cc=bristot@redhat.com \
--cc=bsegall@google.com \
--cc=dietmar.eggemann@arm.com \
--cc=ionela.voinescu@arm.com \
--cc=juri.lelli@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=mgorman@suse.de \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=quic_qiancai@quicinc.com \
--cc=rjw@rjwysocki.net \
--cc=rostedt@goodmis.org \
--cc=sudeep.holla@arm.com \
--cc=vincent.guittot@linaro.org \
--cc=viresh.kumar@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).