[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20220308043615.uamxqylo3mvw4rhs@vireshk-i7>
Date: Tue, 8 Mar 2022 10:06:15 +0530
From: Viresh Kumar <viresh.kumar@...aro.org>
To: Tim Chang <jia-wei.chang@...iatek.com>
Cc: "Rafael J . Wysocki" <rafael@...nel.org>,
Rob Herring <robh+dt@...nel.org>,
Liam Girdwood <lgirdwood@...il.com>,
Mark Brown <broonie@...nel.org>,
Matthias Brugger <matthias.bgg@...il.com>,
linux-pm@...r.kernel.org, devicetree@...r.kernel.org,
linux-kernel@...r.kernel.org, linux-arm-kernel@...ts.infradead.org,
linux-mediatek@...ts.infradead.org, fan.chen@...iatek.com,
louis.yu@...iatek.com, roger.lu@...iatek.com,
Allen-yy.Lin@...iatek.com,
Project_Global_Chrome_Upstream_Group@...iatek.com,
hsinyi@...gle.com
Subject: Re: [PATCH 0/4] cpufreq: mediatek: introduce mtk cpufreq
On 07-03-22, 20:21, Tim Chang wrote:
> CPUFREQ is DVFS driver used for power saving by scaling clock frequency
> and supply voltage of CPUs. This module cooperates with CCI DEVFREQ for
> certain Mediatek SoCs.
Both subject and this log talks as if you are adding a new cpufreq
driver, while what you are doing is just cleanup mostly. This isn't
how it should be done.
You need to be very explicit with what you are doing and make that
change in a separate patch. The cover letter should tell what you are
doing and why.
--
viresh
Powered by blists - more mailing lists