From: "Ilpo Järvinen" <ilpo.jarvinen@linux.intel.com>
To: skhan@linuxfoundation.org, hansg@kernel.org, corbet@lwn.net,
srinivas.pandruvada@linux.intel.com,
Maciej Wieczor-Retman <m.wieczorretman@pm.me>
Cc: linux-kernel@vger.kernel.org,
platform-driver-x86@vger.kernel.org, linux-doc@vger.kernel.org
Subject: Re: [PATCH v3 0/2] platform/x86/intel-uncore-freq: Expose instance ID in the sysfs
Date: Wed, 06 May 2026 16:54:23 +0300 [thread overview]
Message-ID: <177807566314.8094.18400142922022766172.b4-ty@linux.intel.com> (raw)
In-Reply-To: <cover.1775665057.git.m.wieczorretman@pm.me>
On Wed, 08 Apr 2026 16:27:40 +0000, Maciej Wieczor-Retman wrote:
> --- Motivation
>
> This patchset is about exporting instance ID, a value used to uniquely
> identify MMIO blocks in TPMI devices. Userspace tools like "pepc" [1]
> can use it for direct MMIO reads or writes.
>
> Currently exported information allows doing this on non-partitioned
> systems, but partitioned systems require additional steps to map MMIO
> blocks.
>
> [...]
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/2] platform/x86/intel-uncore-freq: Rename instance_id
commit: d8e484a452ca195b7c099373f3c7901bd405b623
[2/2] platform/x86/intel-uncore-freq: Expose instance ID in the sysfs
commit: 6cf1c1e9f21ba2e44e05e691d5241290c7d6c41a
--
i.
next prev parent reply other threads:[~2026-05-06 13:54 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-08 16:27 [PATCH v3 0/2] platform/x86/intel-uncore-freq: Expose instance ID in the sysfs Maciej Wieczor-Retman
2026-04-08 16:27 ` [PATCH v3 1/2] platform/x86/intel-uncore-freq: Rename instance_id Maciej Wieczor-Retman
2026-04-22 15:49 ` srinivas pandruvada
2026-04-08 16:27 ` [PATCH v3 2/2] platform/x86/intel-uncore-freq: Expose instance ID in the sysfs Maciej Wieczor-Retman
2026-04-22 16:17 ` srinivas pandruvada
2026-05-06 13:54 ` Ilpo Järvinen [this message]
2026-05-06 14:08 ` [PATCH v3 0/2] " Maciej Wieczor-Retman
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=177807566314.8094.18400142922022766172.b4-ty@linux.intel.com \
--to=ilpo.jarvinen@linux.intel.com \
--cc=corbet@lwn.net \
--cc=hansg@kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=m.wieczorretman@pm.me \
--cc=platform-driver-x86@vger.kernel.org \
--cc=skhan@linuxfoundation.org \
--cc=srinivas.pandruvada@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