From: "Ilpo Järvinen" <ilpo.jarvinen@linux.intel.com>
To: irenic.rajneesh@gmail.com, david.e.box@linux.intel.com,
platform-driver-x86@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-pm@vger.kernel.org,
Xi Pardee <xi.pardee@linux.intel.com>
Subject: Re: [PATCH v3 0/7] Enable NVL support in intel_pmc_core
Date: Fri, 08 May 2026 21:54:21 +0300 [thread overview]
Message-ID: <177826646106.13514.14306221058288030989.b4-ty@linux.intel.com> (raw)
In-Reply-To: <20260505043342.2573556-1-xi.pardee@linux.intel.com>
On Mon, 04 May 2026 21:33:31 -0700, Xi Pardee wrote:
> This patch series introduces two new features, enhances existing
> functionalities, and adds NVL support to the intel_pmc_core driver.
>
> The first three patches add new attributes to improve Package C-state
> debugging. The fourth and fifth patches refine current functionality
> for better support. The sixth patch enables the intel_pmc_core driver
> retrieves PMC information only for available PMCs. Finally, the last
> patch adds support for Nova Lake platforms.
>
> [...]
Thank you for your contribution, it has been applied to my local
review-ilpo-next branch. Note it will show up in the public
platform-drivers-x86/review-ilpo-next branch only once I've pushed my
local branch there, which might take a while.
The list of commits applied:
[1/7] platform/x86/intel/pmc: Use __free() in pmc_core_punit_pmt_init()
commit: dfe614f82e445a65cb2afd01859b06b01fce8889
[2/7] platform/x86/intel/pmc: Enable PkgC LTR blocking counter
commit: 38c79dd63b72e36919ef097d4e5025ca0fa17f34
[3/7] platform/x86/intel/pmc: Enable Pkgc blocking residency counter
commit: d727eb1c3ede7c21f885ded1f1ad65b47434a9b9
[4/7] platform/x86/intel/pmc: Use PCI DID for PMC SSRAM device discovery
commit: 11de0586ecf40aa747972f1b0bf88bac192d7b06
[5/7] platform/x86/intel/pmc: Add support for variable DMU offsets
commit: ebbf33380896cc489e870d88004ad3750e908a6c
[6/7] platform/x86/intel/pmc: Retrieve PMC info only for available PMCs
commit: a7d5916d132300b1ff6ac0c5f6d7a7cb7817a7fc
[7/7] platform/x86/intel/pmc: Add Nova Lake support to intel_pmc_core driver
commit: 41354f4c8a791d3059f4355945e550693ac87ce8
--
i.
prev parent reply other threads:[~2026-05-08 18:54 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-05 4:33 [PATCH v3 0/7] Enable NVL support in intel_pmc_core Xi Pardee
2026-05-05 4:33 ` [PATCH v3 1/7] platform/x86/intel/pmc: Use __free() in pmc_core_punit_pmt_init() Xi Pardee
2026-05-05 4:33 ` [PATCH v3 2/7] platform/x86/intel/pmc: Enable PkgC LTR blocking counter Xi Pardee
2026-05-05 4:33 ` [PATCH v3 3/7] platform/x86/intel/pmc: Enable Pkgc blocking residency counter Xi Pardee
2026-05-05 4:33 ` [PATCH v3 4/7] platform/x86/intel/pmc: Use PCI DID for PMC SSRAM device discovery Xi Pardee
2026-05-05 4:33 ` [PATCH v3 5/7] platform/x86/intel/pmc: Add support for variable DMU offsets Xi Pardee
2026-05-05 4:33 ` [PATCH v3 6/7] platform/x86/intel/pmc: Retrieve PMC info only for available PMCs Xi Pardee
2026-05-05 4:33 ` [PATCH v3 7/7] platform/x86/intel/pmc: Add Nova Lake support to intel_pmc_core driver Xi Pardee
2026-05-08 18:54 ` Ilpo Järvinen [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=177826646106.13514.14306221058288030989.b4-ty@linux.intel.com \
--to=ilpo.jarvinen@linux.intel.com \
--cc=david.e.box@linux.intel.com \
--cc=irenic.rajneesh@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=platform-driver-x86@vger.kernel.org \
--cc=xi.pardee@linux.intel.com \
/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