From: Guenter Roeck <linux@roeck-us.net>
To: Ivan Mikhaylov <fr0st61te@gmail.com>
Cc: Iwona Winiarska <iwona.winiarska@intel.com>,
linux-hwmon@vger.kernel.org, linux-kernel@vger.kernel.org,
openbmc@lists.ozlabs.org
Subject: Re: [PATCH 2/3] hwmon: (peci/dimmtemp) add Intel Emerald Rapids platform support
Date: Sun, 12 Oct 2025 11:12:32 -0700 [thread overview]
Message-ID: <da2e5d5e-4bd7-46a8-a664-2f5e0d69b28d@roeck-us.net> (raw)
In-Reply-To: <20251006215321.5036-3-fr0st61te@gmail.com>
On Tue, Oct 07, 2025 at 12:53:20AM +0300, Ivan Mikhaylov wrote:
> Extend the functionality of hwmon (peci/dimmtemp) for Emerald Rapids
> platform.
>
> The patch has been tested on a 5S system with 16 DIMMs installed.
> Verified read of DIMM temperature thresholds & temperature.
>
> Using Sapphire's callbacks about getting thresholds because it's same
> platform/socket.
>
> Signed-off-by: Ivan Mikhaylov <fr0st61te@gmail.com>
> Reviewed-by: Paul Menzel <pmenzel@molgen.mpg.de>
Applied to hwmon-next.
Thanks,
Guenter
next prev parent reply other threads:[~2025-10-12 18:12 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-06 21:53 [PATCH 0/3] Add Emerald Rapids PECI support Ivan Mikhaylov
2025-10-06 21:53 ` [PATCH 1/3] peci: cpu: add Intel Emerald Rapids support Ivan Mikhaylov
2025-10-07 8:19 ` Paul Menzel
2025-10-12 18:11 ` Guenter Roeck
2025-10-06 21:53 ` [PATCH 2/3] hwmon: (peci/dimmtemp) add Intel Emerald Rapids platform support Ivan Mikhaylov
2025-10-07 8:26 ` Paul Menzel
2025-10-13 11:44 ` Ivan Mikhaylov
2025-10-13 14:47 ` Guenter Roeck
2025-10-12 18:12 ` Guenter Roeck [this message]
2025-10-06 21:53 ` [PATCH 3/3] hwmon: (peci/cputemp) add Intel Emerald Rapids support Ivan Mikhaylov
2025-10-07 8:31 ` Paul Menzel
2025-10-12 18:13 ` Guenter Roeck
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=da2e5d5e-4bd7-46a8-a664-2f5e0d69b28d@roeck-us.net \
--to=linux@roeck-us.net \
--cc=fr0st61te@gmail.com \
--cc=iwona.winiarska@intel.com \
--cc=linux-hwmon@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=openbmc@lists.ozlabs.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
all inboxes | Powered by JetHome®