[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20230801085228.6f5xley3aybryfjv@vireshk-i7>
Date: Tue, 1 Aug 2023 14:22:28 +0530
From: Viresh Kumar <viresh.kumar@...aro.org>
To: Mario Limonciello <mario.limonciello@....com>
Cc: Meng Li <li.meng@....com>,
"Rafael J . Wysocki" <rafael.j.wysocki@...el.com>,
Huang Rui <ray.huang@....com>, linux-pm@...r.kernel.org,
Shuah Khan <skhan@...uxfoundation.org>,
linux-kselftest@...r.kernel.org,
Nathan Fontenot <nathan.fontenot@....com>,
Deepak Sharma <deepak.sharma@....com>,
Alex Deucher <alexander.deucher@....com>,
Shimmer Huang <shimmer.huang@....com>,
Perry Yuan <Perry.Yuan@....com>,
Xiaojian Du <Xiaojian.Du@....com>,
Borislav Petkov <bp@...en8.de>, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] Modify the function to et the highest_perf value
On 31-07-23, 20:10, Mario Limonciello wrote:
> On 7/31/23 19:47, Meng Li wrote:
> > The previous function will be deprecated.
> >
> > Signed-off-by: Meng Li <li.meng@....com>
> > ---
>
> This actually has functional impact; doesn't it? Can you better describe
> the reasoning and expected impact in the commit message?
Also write the $Subject properly like:
cpufreq: amd-pstate-ut: ...
--
viresh
Powered by blists - more mailing lists