mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Joel GUITTET <jguittet.opensource@witekio.com>
Cc: Thorsten Leemhuis <regressions@leemhuis.info>,
	Jay Buddhabhatti <jay.buddhabhatti@amd.com>,
	Linux kernel regressions list <regressions@lists.linux.dev>,
	Sasha Levin <sashal@kernel.org>, Stephen Boyd <sboyd@kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"stable@vger.kernel.org" <stable@vger.kernel.org>
Subject: Re: Bad commit backported on the v5.15.y branch ?
Date: Wed, 16 Oct 2024 16:58:29 +0200	[thread overview]
Message-ID: <2024101632-outspoken-tabby-8ad9@gregkh> (raw)
In-Reply-To: <AM9P192MB13167529B6C73DC8686C2F86D7462@AM9P192MB1316.EURP192.PROD.OUTLOOK.COM>

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

      reply	other threads:[~2024-10-16 14:58 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-10-11  8:48 Joel GUITTET
2024-10-14  6:45 ` Thorsten Leemhuis
2024-10-16  9:23   ` Joel GUITTET
2024-10-16 10:53     ` Greg KH
2024-10-16 13:13       ` Joel GUITTET
2024-10-16 14:58         ` Greg KH [this message]

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=2024101632-outspoken-tabby-8ad9@gregkh \
    --to=gregkh@linuxfoundation.org \
    --cc=jay.buddhabhatti@amd.com \
    --cc=jguittet.opensource@witekio.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=regressions@leemhuis.info \
    --cc=regressions@lists.linux.dev \
    --cc=sashal@kernel.org \
    --cc=sboyd@kernel.org \
    --cc=stable@vger.kernel.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
all inboxes | Powered by JetHome®