From: "Ilpo Järvinen" <ilpo.jarvinen@linux.intel.com>
To: hansg@kernel.org, Krishna Chomal <krishna.chomal108@gmail.com>
Cc: platform-driver-x86@vger.kernel.org,
linux-kernel@vger.kernel.org, Yahia Ahmed <yahmedd043@gmail.com>,
stable@vger.kernel.org
Subject: Re: [PATCH] platform/x86: hp-wmi: Add support for OMEN MAX 16-ak0xxx (8DD6)
Date: Tue, 07 Jul 2026 20:08:16 +0300 [thread overview]
Message-ID: <178344409637.17784.435700941911534714.b4-ty@b4> (raw)
In-Reply-To: <20260623141314.33947-1-krishna.chomal108@gmail.com>
On Tue, 23 Jun 2026 19:43:14 +0530, Krishna Chomal wrote:
> The HP OMEN MAX 16-ak0xxx (board ID: 8DD6) has the same WMI interface
> as other Victus S boards, but requires quirks for correctly switching
> thermal profile.
>
> After testing we know that (similar to another HP Omen Max 16 device,
> board ID 8D87), the embedded controller on this board does not expose
> thermal profile which means we have to intentionally disable EC readback.
>
> [...]
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.
FYI [if applicable to your patch], as per Linus' policy change, also
fixes are mostly routed through for-next unless the fix is for a
commit introduced in the most recent cycle or is clearly a regression
fix.
The list of commits applied:
[1/1] platform/x86: hp-wmi: Add support for OMEN MAX 16-ak0xxx (8DD6)
commit: 44dc7fcb32791e9144a7024075af6cf999f81e81
--
i.
prev parent reply other threads:[~2026-07-07 17:08 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-23 14:13 Krishna Chomal
2026-07-07 17:08 ` 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=178344409637.17784.435700941911534714.b4-ty@b4 \
--to=ilpo.jarvinen@linux.intel.com \
--cc=hansg@kernel.org \
--cc=krishna.chomal108@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=platform-driver-x86@vger.kernel.org \
--cc=stable@vger.kernel.org \
--cc=yahmedd043@gmail.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®