The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: "M, Krishnamoorthi" <krishnamoorthi.m@amd.com>
To: "Ilpo Järvinen" <ilpo.jarvinen@linux.intel.com>
Cc: mario.limonciello@amd.com, Hans de Goede <hansg@kernel.org>,
	Shyam-sundar.S-k@amd.com, perry.yuan@amd.com,
	platform-driver-x86@vger.kernel.org,
	LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] platform/x86/amd: hfi: Support for ranking table versions
Date: Wed, 13 May 2026 01:24:52 +0530	[thread overview]
Message-ID: <ea4a2d8a-297d-4724-a0cd-4d0e4eac1036@amd.com> (raw)
In-Reply-To: <cb917e96-db3e-baf8-91a0-8bba4ba97208@linux.intel.com>

Hi,

On 5/11/2026 7:50 PM, Ilpo Järvinen wrote:
> On Fri, 8 May 2026, Krishnamoorthi M wrote:
>
>> Add changes to support new ranking table version. Version 2 of the
>> heterogeneous ranking table provides static CPU rankings. Version 3 adds
>> dynamic ranking table support on newer AMD platforms. These changes ensure
>> that platforms still reporting version 2 continue to function with the
>> existing static ranking path, avoiding regressions on older hardware
>> that does not supply a dynamic ranking table.
>>
>> Signed-off-by: Krishnamoorthi M <krishnamoorthi.m@amd.com>
> Hi,
>
> Don't we want to have Cc: stable@vger.kernel.org # 6.17 for this?
No, Cc: stable is not required. This change enables ranking table 
support for upcoming AMD platforms(which reports table version 3), so 
there is no issue to address on stable.

Thanks,
Krishna
>
> (I can add it if that's the case, no need to resubmit because of it.)
>

      reply	other threads:[~2026-05-12 19:55 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-05-07 19:09 [PATCH] platform/x86/amd: hfi: Support for ranking table versions Krishnamoorthi M
2026-05-07 19:25 ` Mario Limonciello
2026-05-08 10:11 ` Shyam Sundar S K
2026-05-11 14:20 ` Ilpo Järvinen
2026-05-12 19:54   ` M, Krishnamoorthi [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=ea4a2d8a-297d-4724-a0cd-4d0e4eac1036@amd.com \
    --to=krishnamoorthi.m@amd.com \
    --cc=Shyam-sundar.S-k@amd.com \
    --cc=hansg@kernel.org \
    --cc=ilpo.jarvinen@linux.intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mario.limonciello@amd.com \
    --cc=perry.yuan@amd.com \
    --cc=platform-driver-x86@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