From: Viresh Kumar <viresh.kumar@linaro.org>
To: "Rafael J. Wysocki" <rafael@kernel.org>
Cc: Matthias Brugger <matthias.bgg@gmail.com>,
linux-pm@vger.kernel.org,
Vincent Guittot <vincent.guittot@linaro.org>,
regressions@leemhuis.info, daniel@makrotopia.org,
thomas.huehn@hs-nordhausen.de,
"v5 . 19+" <stable@vger.kernel.org>, Nick <vincent@systemli.org>,
linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-mediatek@lists.infradead.org
Subject: Re: [PATCH] Revert "cpufreq: mediatek: Refine mtk_cpufreq_voltage_tracking()"
Date: Tue, 6 Dec 2022 05:00:59 +0530 [thread overview]
Message-ID: <20221205233059.izdqcilbhjmkh6ew@vireshk-i7> (raw)
In-Reply-To: <CAJZ5v0gTV5LM_qRKncPq5Z2TRENMgVer6oZiGAKJn6ndrNSKxg@mail.gmail.com>
On 05-12-22, 13:08, Rafael J. Wysocki wrote:
> Well, this was a bit unclear.
Hmm, yeah. I assumed that the arm stuff will go via my tree and you
will be in sync with this. But yeah, a comment in the patch won't have
hurt.
> Alright then, I'll assume that the proper fix will come in through
> your pull request for 6.2 (but please send that one before the merge
> window opens), thanks!
I was ready with pull request since several days, was just waiting for
this to get sorted out. And I think this may get delayed a bit too, so
I better send the first pull request now and worry about this later.
--
viresh
next prev parent reply other threads:[~2022-12-05 23:31 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <930778a1-5e8b-6df6-3276-42dcdadaf682@systemli.org>
2022-12-02 5:26 ` [PATCH] Revert "cpufreq: mediatek: Refine mtk_cpufreq_voltage_tracking()" Viresh Kumar
2022-12-02 12:17 ` Rafael J. Wysocki
2022-12-02 19:46 ` Rafael J. Wysocki
2022-12-05 4:30 ` Viresh Kumar
2022-12-05 12:08 ` Rafael J. Wysocki
2022-12-05 23:30 ` Viresh Kumar [this message]
2022-12-02 12:47 ` Nick
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=20221205233059.izdqcilbhjmkh6ew@vireshk-i7 \
--to=viresh.kumar@linaro.org \
--cc=daniel@makrotopia.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=linux-pm@vger.kernel.org \
--cc=matthias.bgg@gmail.com \
--cc=rafael@kernel.org \
--cc=regressions@leemhuis.info \
--cc=stable@vger.kernel.org \
--cc=thomas.huehn@hs-nordhausen.de \
--cc=vincent.guittot@linaro.org \
--cc=vincent@systemli.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).