All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mario Limonciello <mario.limonciello@amd.com>
To: "Rafael J. Wysocki" <rafael@kernel.org>
Cc: Linux PM <linux-pm@vger.kernel.org>
Subject: [GIT PULL] amd-pstate fixes for v6.14-rc (2/6/25)
Date: Thu, 6 Feb 2025 13:32:07 -0600	[thread overview]
Message-ID: <e656ef9c-3e77-4a40-912f-cee96632bbb7@amd.com> (raw)

Hello,

The following changes since commit 2014c95afecee3e76ca4a56956a936e23283f05b:

   Linux 6.14-rc1 (2025-02-02 15:39:26 -0800)

are available in the Git repository at:

  
ssh://git@gitolite.kernel.org/pub/scm/linux/kernel/git/superm1/linux.git 
tags/amd-pstate-v6.14-2025-02-06

for you to fetch changes up to 3ace20038e19f23fe73259513f1f08d4bf1a3c83:

   cpufreq/amd-pstate: Fix cpufreq_policy ref counting (2025-02-06 
13:19:36 -0600)

----------------------------------------------------------------
amd-pstate fixes 2/6/25

* Fix some error cleanup paths with mutex use and boost
* Fix a ref counting issue
* Fix a schedutil issue

----------------------------------------------------------------
Dhananjay Ugwekar (3):
       cpufreq/amd-pstate: Remove the goto label in amd_pstate_update_limits
       cpufreq/amd-pstate: Fix max_perf updation with schedutil
       cpufreq/amd-pstate: Fix cpufreq_policy ref counting

Lifeng Zheng (1):
       cpufreq/amd-pstate: Fix per-policy boost flag incorrect when fail

  drivers/cpufreq/amd-pstate.c | 20 ++++++++++----------
  1 file changed, 10 insertions(+), 10 deletions(-)

             reply	other threads:[~2025-02-06 19:32 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-02-06 19:32 Mario Limonciello [this message]
2025-02-06 19:42 ` [GIT PULL] amd-pstate fixes for v6.14-rc (2/6/25) Rafael J. Wysocki

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=e656ef9c-3e77-4a40-912f-cee96632bbb7@amd.com \
    --to=mario.limonciello@amd.com \
    --cc=linux-pm@vger.kernel.org \
    --cc=rafael@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.