From: Dave Hansen <dave.hansen@intel.com>
To: Sohil Mehta <sohil.mehta@intel.com>, Guenter Roeck <linux@roeck-us.net>
Cc: Dave Hansen <dave.hansen@linux.intel.com>,
linux-hwmon@vger.kernel.org,
Srinivas Pandruvada <srinivas.pandruvada@linux.intel.com>,
Ricardo Neri <ricardo.neri-calderon@linux.intel.com>,
Zhang Rui <rui.zhang@intel.com>,
x86@kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3] hwmon: (coretemp) Replace x86_model checks with VFM ones
Date: Thu, 28 Aug 2025 14:51:37 -0700 [thread overview]
Message-ID: <fa0f4052-22cd-47cc-95ea-ffe1c3a5a52a@intel.com> (raw)
In-Reply-To: <c53dedd1-5c58-4325-8da8-552f109b67c5@intel.com>
On 8/28/25 14:45, Sohil Mehta wrote:
> On 8/28/2025 2:42 PM, Guenter Roeck wrote:
...
> Dave has provided his signoff on the patch now. Also, he suggested
> including a Cc: stable.
Let's just wait until Guenter sends it upstream. Once it hits Linus's
tree, you can ask for it to be in stable if we decide it's a good idea.
I asked if it was necessary because I'm not positive it's a good idea.
For instance, if the model numbers in play were all >100 and Intel has
zero plans to introduce a family 18/19, model >100, then it might not be
worth it. Or, if the only downside is a single warning on dmesg, it
might not be worth it.
But, if it's going to spew warnings constantly or set your brand new
machine ablaze, then maybe it's worth backporting.
So, let's actually look at what it would mean in practice to have it hit
stable@ or not. Just spent 10 minutes looking at it.
next prev parent reply other threads:[~2025-08-28 21:51 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-28 20:17 Sohil Mehta
2025-08-28 21:18 ` Dave Hansen
2025-08-28 21:43 ` Sohil Mehta
2025-08-28 21:47 ` Guenter Roeck
2025-08-28 21:42 ` Guenter Roeck
2025-08-28 21:45 ` Sohil Mehta
2025-08-28 21:51 ` Dave Hansen [this message]
2025-08-28 22:33 ` Sohil Mehta
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=fa0f4052-22cd-47cc-95ea-ffe1c3a5a52a@intel.com \
--to=dave.hansen@intel.com \
--cc=dave.hansen@linux.intel.com \
--cc=linux-hwmon@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=ricardo.neri-calderon@linux.intel.com \
--cc=rui.zhang@intel.com \
--cc=sohil.mehta@intel.com \
--cc=srinivas.pandruvada@linux.intel.com \
--cc=x86@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
all inboxes | Powered by JetHome®