From: Emre Cecanpunar <emreleno@gmail.com>
To: platform-driver-x86@vger.kernel.org, hansg@kernel.org,
ilpo.jarvinen@linux.intel.com
Cc: linux-kernel@vger.kernel.org, krishna.chomal108@gmail.com,
radheykalra901@gmail.com, edip@medip.dev, hello@kursatabayli.dev,
mjg59@srcf.ucam.org, akpm@linux-foundation.org,
jorge.lopez2@hp.com, jes965@nyu.edu, mario.limonciello@amd.com,
julien.robin28@free.fr
Subject: Re: [PATCH 0/5] platform/x86: hp-wmi: Fix WMI error handling
Date: Tue, 21 Jul 2026 19:14:48 +0300 [thread overview]
Message-ID: <5b4963cf-7603-4844-a46d-67613e922425@gmail.com> (raw)
In-Reply-To: <cover.1784195117.git.emreleno@gmail.com>
Hi,
Thanks for the review.
These issues were found through code inspection, and I do not currently
have hardware reports reproducing the firmware error paths.
I will drop this series for now and wait for the hp-wmi migration to the
newer WMI API, since that work may address some of these issues more
appropriately.
Regards,
Emre
next prev parent reply other threads:[~2026-07-21 16:14 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-16 9:54 [PATCH 0/5] platform/x86: hp-wmi: Fix WMI error handling Emre Cecanpunar
2026-07-16 9:54 ` [PATCH 1/5] platform/x86: hp-wmi: validate WMI response header size Emre Cecanpunar
2026-07-21 15:42 ` Ilpo Järvinen
2026-07-16 9:54 ` [PATCH 2/5] platform/x86: hp-wmi: handle firmware errors in tablet mode query Emre Cecanpunar
2026-07-21 15:50 ` Ilpo Järvinen
2026-07-16 9:54 ` [PATCH 3/5] platform/x86: hp-wmi: handle errors in the OMEN key event Emre Cecanpunar
2026-07-21 15:52 ` Ilpo Järvinen
2026-07-16 9:54 ` [PATCH 4/5] platform/x86: hp-wmi: normalize GPU thermal mode errors Emre Cecanpunar
2026-07-21 15:57 ` Ilpo Järvinen
2026-07-16 9:54 ` [PATCH 5/5] platform/x86: hp-wmi: report fan speed command failures Emre Cecanpunar
2026-07-21 15:58 ` Ilpo Järvinen
2026-07-21 16:14 ` Emre Cecanpunar [this message]
2026-07-21 16:15 ` [PATCH 0/5] platform/x86: hp-wmi: Fix WMI error handling Emre Cecanpunar
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=5b4963cf-7603-4844-a46d-67613e922425@gmail.com \
--to=emreleno@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=edip@medip.dev \
--cc=hansg@kernel.org \
--cc=hello@kursatabayli.dev \
--cc=ilpo.jarvinen@linux.intel.com \
--cc=jes965@nyu.edu \
--cc=jorge.lopez2@hp.com \
--cc=julien.robin28@free.fr \
--cc=krishna.chomal108@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mario.limonciello@amd.com \
--cc=mjg59@srcf.ucam.org \
--cc=platform-driver-x86@vger.kernel.org \
--cc=radheykalra901@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