public inbox for stable@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Mario Limonciello <superm1@kernel.org>
Cc: "stable@vger.kernel.org" <stable@vger.kernel.org>,
	"Gong, Richard" <Richard.Gong@amd.com>
Subject: Re: AMD PMF on 6.11.y
Date: Sat, 9 Nov 2024 17:53:55 +0100	[thread overview]
Message-ID: <2024110944-excuse-reach-68c4@gregkh> (raw)
In-Reply-To: <da9f1725-01b8-4630-a768-82800f1cc08a@kernel.org>

On Sat, Nov 09, 2024 at 10:48:37AM -0600, Mario Limonciello wrote:
> 
> 
> On 11/9/24 09:30, Greg KH wrote:
> > On Wed, Nov 06, 2024 at 11:52:58PM -0600, Mario Limonciello wrote:
> > > Hi,
> > > 
> > > 6.11 already supports most functionality of AMD family 0x1a model 0x60, but
> > > the amd-pmf driver doesn't load due to a missing device ID.
> > > 
> > > The device ID was added in 6.12 with:
> > > 
> > > commit 8ca8d07857c69 ("platform/x86/amd/pmf: Add SMU metrics table support
> > > for 1Ah family 60h model")
> > > 
> > > Can this please come back to 6.11.y to enable it more widely?
> > 
> > I would be glad to, but it does not apply cleanly, are you sure you
> > tried this?
> > 
> > thanks,
> > 
> > greg k-h
> 
> Whoops! I had thought we had the context changes already in 6.11.y and got
> fooled by the one line change.
> 
> Here's the correct series.
> 
> commit 375780541739 ("platform/x86/amd/pmf: Relocate CPU ID macros to the
> PMF header")
> commit 8f2407cb3f1e ("platform/x86/amd/pmf: Update SMU metrics table for 1AH
> family series")
> commit 8ca8d07857c6 ("platform/x86/amd/pmf: Add SMU metrics table support
> for 1Ah family 60h model")

Much better thanks!  All now queued up.

greg k-h

      reply	other threads:[~2024-11-09 16:53 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-11-07  5:52 AMD PMF on 6.11.y Mario Limonciello
2024-11-09 15:30 ` Greg KH
2024-11-09 16:48   ` Mario Limonciello
2024-11-09 16:53     ` 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=2024110944-excuse-reach-68c4@gregkh \
    --to=gregkh@linuxfoundation.org \
    --cc=Richard.Gong@amd.com \
    --cc=stable@vger.kernel.org \
    --cc=superm1@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