From: "Ilpo Järvinen" <ilpo.jarvinen@linux.intel.com>
To: hdegoede@redhat.com, Armin Wolf <W_Armin@gmx.de>
Cc: platform-driver-x86@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/4] platform/x86: wmi: Check if WMxx control method exists
Date: Wed, 07 Feb 2024 15:52:37 +0200 [thread overview]
Message-ID: <170731395760.2085.5086221738289789312.b4-ty@linux.intel.com> (raw)
In-Reply-To: <20240206220447.3102-1-W_Armin@gmx.de>
On Tue, 06 Feb 2024 23:04:44 +0100, Armin Wolf wrote:
> Some devices like the MSI GF63-12VF contain WMI method blocks
> without providing the necessary WMxx ACPI control methods.
> Avoid creating WMI devices for such WMI method blocks since
> the resulting WMI device is going to be unusable.
>
>
Thank you for your contribution, it has been applied to my local
review-ilpo branch. Note it will show up in the public
platform-drivers-x86/review-ilpo branch only once I've pushed my
local branch there, which might take a while.
The list of commits applied:
[1/4] platform/x86: wmi: Check if WMxx control method exists
commit: 7f1b998a9108f7fd465039323d5fc2599b8cae77
[2/4] platform/x86: wmi: Use FW_BUG when warning about missing control methods
commit: d0c595a11785573aad3b9e32ae293c48757eceff
[3/4] platform/x86: wmi: Remove unnecessary out-of-memory message
commit: 49c67cd5b6a4b611ac775de3831f5e739dd580f2
[4/4] platform/x86: wmi: Replace pr_err() with dev_err()
commit: fde7da1072f3c0239a80b590e7b75c9411e8b630
--
i.
prev parent reply other threads:[~2024-02-07 13:52 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-06 22:04 Armin Wolf
2024-02-06 22:04 ` [PATCH 2/4] platform/x86: wmi: Use FW_BUG when warning about missing control methods Armin Wolf
2024-02-06 22:04 ` [PATCH 3/4] platform/x86: wmi: Remove unnecessary out-of-memory message Armin Wolf
2024-02-06 22:04 ` [PATCH 4/4] platform/x86: wmi: Replace pr_err() with dev_err() Armin Wolf
2024-02-07 13:52 ` 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=170731395760.2085.5086221738289789312.b4-ty@linux.intel.com \
--to=ilpo.jarvinen@linux.intel.com \
--cc=W_Armin@gmx.de \
--cc=hdegoede@redhat.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®