From: Guenter Roeck <linux@roeck-us.net>
To: Armin Wolf <W_Armin@gmx.de>
Cc: Dell.Client.Kernel@dell.com, pali@kernel.org,
mjg59@srcf.ucam.org, hansg@kernel.org,
ilpo.jarvinen@linux.intel.com,
platform-driver-x86@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-hwmon@vger.kernel.org
Subject: Re: [PATCH v2 6/9] hwmon: (dell-smm) Use new buffer-based WMI API
Date: Fri, 13 Mar 2026 11:33:30 -0700 [thread overview]
Message-ID: <07346e6f-8764-43f8-b63c-31dfa9c65add@roeck-us.net> (raw)
In-Reply-To: <20260308200155.118950-7-W_Armin@gmx.de>
On Sun, Mar 08, 2026 at 09:01:52PM +0100, Armin Wolf wrote:
> Use the new buffer-based WMI API to also support ACPI firmware
> implementations that do not use ACPI buffers for returning the
> results of a SMM call.
>
> Signed-off-by: Armin Wolf <W_Armin@gmx.de>
Acked-by: Guenter Roeck <linux@roeck-us.net>
next prev parent reply other threads:[~2026-03-13 18:33 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-08 20:01 [PATCH v2 0/9] Convert most Dell WMI drivers to use the new buffer-based API Armin Wolf
2026-03-08 20:01 ` [PATCH v2 1/9] platform/x86: dell-descriptor: Use new buffer-based WMI API Armin Wolf
2026-03-08 20:01 ` [PATCH v2 2/9] platform/x86: dell-privacy: " Armin Wolf
2026-03-08 20:01 ` [PATCH v2 3/9] platform/x86: dell-smbios-wmi: " Armin Wolf
2026-03-08 20:01 ` [PATCH v2 4/9] platform/x86: dell-wmi-base: " Armin Wolf
2026-03-08 20:01 ` [PATCH v2 5/9] platform/x86: dell-ddv: " Armin Wolf
2026-03-08 20:01 ` [PATCH v2 6/9] hwmon: (dell-smm) " Armin Wolf
2026-03-13 18:33 ` Guenter Roeck [this message]
2026-03-08 20:01 ` [PATCH v2 7/9] platform/wmi: Make wmi_bus_class const Armin Wolf
2026-03-08 20:01 ` [PATCH v2 8/9] platform/wmi: Make sysfs attributes const Armin Wolf
2026-03-08 20:01 ` [PATCH v2 9/9] modpost: Handle malformed WMI GUID strings Armin Wolf
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=07346e6f-8764-43f8-b63c-31dfa9c65add@roeck-us.net \
--to=linux@roeck-us.net \
--cc=Dell.Client.Kernel@dell.com \
--cc=W_Armin@gmx.de \
--cc=hansg@kernel.org \
--cc=ilpo.jarvinen@linux.intel.com \
--cc=linux-hwmon@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mjg59@srcf.ucam.org \
--cc=pali@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®