From: "Ilpo Järvinen" <ilpo.jarvinen@linux.intel.com>
To: Rajneesh Bhardwaj <irenic.rajneesh@gmail.com>,
"David E . Box" <david.e.box@linux.intel.com>,
Yousef Alhouseen <alhouseenyousef@gmail.com>
Cc: platform-driver-x86@vger.kernel.org,
linux-kernel@vger.kernel.org, Hans de Goede <hansg@kernel.org>
Subject: Re: [PATCH] platform/x86/intel/pmc: initialize empty PMT read result
Date: Tue, 21 Jul 2026 20:16:12 +0300 [thread overview]
Message-ID: <178465417246.18499.14956271722010713784.b4-ty@b4> (raw)
In-Reply-To: <20260630105101.54016-1-alhouseenyousef@gmail.com>
On Tue, 30 Jun 2026 12:51:01 +0200, Yousef Alhouseen wrote:
> pmc_core_pmt_get_lpm_req() returns the last telemetry read status. When
> firmware exposes no enabled low-power modes, the loop does not run
> and the function returns an uninitialized stack value.
>
> Initialize the status to success so an empty mode set is handled
> deterministically.
>
> [...]
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/intel/pmc: initialize empty PMT read result
commit: 408b87a481e3ab33cba00292e4c80a30ba97f995
--
i.
prev parent reply other threads:[~2026-07-21 17:16 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-30 10:51 Yousef Alhouseen
2026-07-10 16:12 ` David Box
2026-07-21 17:16 ` 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=178465417246.18499.14956271722010713784.b4-ty@b4 \
--to=ilpo.jarvinen@linux.intel.com \
--cc=alhouseenyousef@gmail.com \
--cc=david.e.box@linux.intel.com \
--cc=hansg@kernel.org \
--cc=irenic.rajneesh@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=platform-driver-x86@vger.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®