From: Paul Menzel <pmenzel@molgen.mpg.de>
To: Naresh Solanki <naresh.solanki@9elements.com>
Cc: linux-kernel@vger.kernel.org, linux-hwmon@vger.kernel.org,
iwona.winiarska@intel.com, linux@roeck-us.net, jdelvare@suse.com,
openbmc@lists.ozlabs.org,
Patrick Rudolph <patrick.rudolph@9elements.com>
Subject: Re: [PATCH v2 1/3] peci: cpu: Add Intel Sapphire Rapids support
Date: Wed, 19 Jul 2023 13:20:20 +0200 [thread overview]
Message-ID: <c1988d23-c19c-0ec0-9f61-01cbb00ead3a@molgen.mpg.de> (raw)
In-Reply-To: <20230712091241.3668454-1-Naresh.Solanki@9elements.com>
Dear Naresh,
Thank you for the patch.
Am 12.07.23 um 11:12 schrieb Naresh Solanki:
> Add support for detection of Intel Sapphire Rapids processor based on
> CPU family & model.
>
> Sapphire Rapids Xeon processors with the family set to 6 and the
> model set to INTEL_FAM6_SAPPHIRERAPIDS_X. The data field for this entry
> is "spr".
Please add, how you tested this.
> Signed-off-by: Patrick Rudolph <patrick.rudolph@9elements.com>
> Signed-off-by: Naresh Solanki <Naresh.Solanki@9elements.com>
> ---
> Changes in V2:
> - Refactored from previous patchset as seperate patch based on subsystem.
> ---
> drivers/peci/cpu.c | 5 +++++
> 1 file changed, 5 insertions(+)
>
> diff --git a/drivers/peci/cpu.c b/drivers/peci/cpu.c
> index de4a7b3e5966..3668a908d259 100644
> --- a/drivers/peci/cpu.c
> +++ b/drivers/peci/cpu.c
> @@ -318,6 +318,11 @@ static const struct peci_device_id peci_cpu_device_ids[] = {
> .model = INTEL_FAM6_ICELAKE_X,
> .data = "icx",
> },
> + { /* Sapphire Rapids Xeon */
> + .family = 6,
> + .model = INTEL_FAM6_SAPPHIRERAPIDS_X,
> + .data = "spr",
> + },
> { /* Icelake Xeon D */
> .family = 6,
> .model = INTEL_FAM6_ICELAKE_D,
It looks like it’s incorrectly sorted, probably due to merge conflict
resolution?
Kind regards,
Paul
next prev parent reply other threads:[~2023-07-19 11:21 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-12 9:12 Naresh Solanki
2023-07-12 9:12 ` [PATCH v2 2/3] hwmon: (peci/cputemp) " Naresh Solanki
2023-07-19 13:34 ` Guenter Roeck
2023-07-20 13:09 ` Winiarska, Iwona
2023-07-12 9:12 ` [PATCH v2 3/3] hwmon: (peci/dimmtemp) Add " Naresh Solanki
2023-07-19 13:36 ` Guenter Roeck
2023-07-19 11:20 ` Paul Menzel [this message]
2023-07-19 12:17 ` [PATCH v2 1/3] peci: cpu: Add Intel " Naresh Solanki
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=c1988d23-c19c-0ec0-9f61-01cbb00ead3a@molgen.mpg.de \
--to=pmenzel@molgen.mpg.de \
--cc=iwona.winiarska@intel.com \
--cc=jdelvare@suse.com \
--cc=linux-hwmon@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=naresh.solanki@9elements.com \
--cc=openbmc@lists.ozlabs.org \
--cc=patrick.rudolph@9elements.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
all inboxes | Powered by JetHome®