[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID:
<AM9P192MB13167529B6C73DC8686C2F86D7462@AM9P192MB1316.EURP192.PROD.OUTLOOK.COM>
Date: Wed, 16 Oct 2024 13:13:42 +0000
From: Joel GUITTET <jguittet.opensource@...ekio.com>
To: Greg KH <gregkh@...uxfoundation.org>
CC: Thorsten Leemhuis <regressions@...mhuis.info>, Jay Buddhabhatti
<jay.buddhabhatti@....com>, Linux kernel regressions list
<regressions@...ts.linux.dev>, Sasha Levin <sashal@...nel.org>, Stephen Boyd
<sboyd@...nel.org>, "linux-kernel@...r.kernel.org"
<linux-kernel@...r.kernel.org>, "stable@...r.kernel.org"
<stable@...r.kernel.org>
Subject: RE: Bad commit backported on the v5.15.y branch ?
> Because it has a "Fixes:" tag on it. Is that tag not correct?
understood why it's backported. Probably yes. Or maybe another commit should be introduced to not create a new issue.
> What "original message"?
My original message in this mailing list, see below commands that show the problem (last line is wrong):
cat /sys/devices/system/cpu/cpufreq/policy0/scaling_available_frequencies
299999 399999 599999 1199999
echo 399999 > /sys/devices/system/cpu/cpufreq/policy0/scaling_setspeed
cat /sys/devices/system/cpu/cpufreq/policy0/scaling_cur_freq
399999
cat /sys/devices/system/cpu/cpufreq/policy0/cpuinfo_cur_freq
299999 ====> Should be 399999
Powered by blists - more mailing lists