From: Randy Dunlap <rdunlap@infradead.org>
To: Armin Wolf <W_Armin@gmx.de>,
ilpo.jarvinen@linux.intel.com, hdegoede@redhat.com,
chumuzero@gmail.com, corbet@lwn.net, cs@tuxedo.de,
wse@tuxedocomputers.com, ggo@tuxedocomputers.com
Cc: linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org,
platform-driver-x86@vger.kernel.org
Subject: Re: [RFC PATCH 1/3] platform/x86: Add Uniwill WMI driver
Date: Sun, 15 Jun 2025 13:32:04 -0700 [thread overview]
Message-ID: <d86a489c-8895-43c2-9968-1c0c6972c828@infradead.org> (raw)
In-Reply-To: <20250615175957.9781-2-W_Armin@gmx.de>
On 6/15/25 10:59 AM, Armin Wolf wrote:
> diff --git a/Documentation/wmi/devices/uniwill-wmi.rst b/Documentation/wmi/devices/uniwill-wmi.rst
> new file mode 100644
> index 000000000000..232fa8349611
> --- /dev/null
> +++ b/Documentation/wmi/devices/uniwill-wmi.rst
> @@ -0,0 +1,52 @@
> +.. SPDX-License-Identifier: GPL-2.0-or-later
> +
> +======================================
> +Uniwill WMI event driver (uniwill-wmi)
> +======================================
> +
> +Introduction
> +============
> +
> +Many notebooks manufactured by Uniwill (either directly or as ODM) provide an WMI-based
a WMI-based
> +event interface for various platform events like hotkeys. This interface is used by the
> +``uniwill-wmi`` driver to react to hotkey presses.
--
~Randy
next prev parent reply other threads:[~2025-06-15 20:32 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-15 17:59 [RFC PATCH 0/3] platform/x86: Add support for Uniwill laptop features Armin Wolf
2025-06-15 17:59 ` [RFC PATCH 1/3] platform/x86: Add Uniwill WMI driver Armin Wolf
2025-06-15 18:46 ` Randy Dunlap
2025-06-15 19:05 ` ALOK TIWARI
2025-06-17 20:58 ` Armin Wolf
2025-06-15 20:32 ` Randy Dunlap [this message]
2025-06-16 9:21 ` Hans de Goede
2025-06-17 21:10 ` Armin Wolf
2025-06-18 7:23 ` Hans de Goede
2025-06-16 11:14 ` Werner Sembach
2025-06-15 17:59 ` [RFC PATCH 2/3] platform/x86: Add Uniwill laptop driver Armin Wolf
2025-06-15 19:00 ` Randy Dunlap
2025-06-17 21:40 ` Armin Wolf
2025-06-15 20:39 ` Randy Dunlap
2025-06-16 8:10 ` Ilpo Järvinen
2025-06-17 21:47 ` Armin Wolf
2025-06-16 12:32 ` Werner Sembach
2025-06-17 21:50 ` Armin Wolf
2025-06-18 11:15 ` Werner Sembach
2025-06-22 18:58 ` Armin Wolf
2025-06-16 12:46 ` Werner Sembach
2025-06-17 21:52 ` Armin Wolf
2025-06-19 9:47 ` Lee Jones
2025-06-19 12:30 ` Hans de Goede
2025-06-19 15:17 ` Lee Jones
2025-06-19 20:03 ` Hans de Goede
2025-06-22 19:19 ` Armin Wolf
2025-06-22 21:37 ` Pőcze Barnabás
2025-06-22 22:36 ` Armin Wolf
2025-06-25 15:59 ` Pőcze Barnabás
2025-06-27 23:09 ` Armin Wolf
2025-06-30 12:32 ` Werner Sembach
2025-06-30 12:40 ` Armin Wolf
2025-06-30 12:55 ` Werner Sembach
2025-06-30 13:21 ` Armin Wolf
2025-06-15 17:59 ` [RFC PATCH 3/3] Documentation: laptops: Add documentation for uniwill laptops Armin Wolf
2025-06-18 6:23 ` Randy Dunlap
2025-06-18 20:06 ` Armin Wolf
2025-06-16 12:59 ` [RFC PATCH 0/3] platform/x86: Add support for Uniwill laptop features Werner Sembach
2025-06-17 22:02 ` 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=d86a489c-8895-43c2-9968-1c0c6972c828@infradead.org \
--to=rdunlap@infradead.org \
--cc=W_Armin@gmx.de \
--cc=chumuzero@gmail.com \
--cc=corbet@lwn.net \
--cc=cs@tuxedo.de \
--cc=ggo@tuxedocomputers.com \
--cc=hdegoede@redhat.com \
--cc=ilpo.jarvinen@linux.intel.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=platform-driver-x86@vger.kernel.org \
--cc=wse@tuxedocomputers.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;
as well as URLs for NNTP newsgroup(s).