Re: Bad commit backported on the v5.15.y branch ?

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Wed, Oct 16, 2024 at 01:13:42PM +0000, Joel GUITTET wrote:
> > 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.

Perhaps, but I have no clue what is going on here, sorry.

Is this an issue in Linus's tree?  Is it in the other stable releases?
If not, are we missing a change?  Or does the issue show up there as
well?

> > 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

Ok, so someone needs to tell me what to do here as I'm confused :)

thanks,

greg k-h




[Index of Archives]     [Linux Kernel]     [Kernel Development Newbies]     [Linux USB Devel]     [Video for Linux]     [Linux Audio Users]     [Yosemite Hiking]     [Linux Kernel]     [Linux SCSI]

  Powered by Linux