From: Andy Lutomirski <luto@kernel.org>
To: Darren Hart <dvhart@infradead.org>
Cc: "Matthew Garrett" <mjg59@srcf.ucam.org>,
linux-acpi@vger.kernel.org, platform-driver-x86@vger.kernel.org,
"Mario Limonciello" <mario_limonciello@dell.com>,
"Pali Rohár" <pali.rohar@gmail.com>,
"Andy Lutomirski" <luto@kernel.org>
Subject: [PATCH 00/14] Big WMI driver rework
Date: Mon, 30 Nov 2015 17:05:50 -0800 [thread overview]
Message-ID: <cover.1448931782.git.luto@kernel.org> (raw)
Here's v1. I'm sure it still needs work. Thoughts?
Andy Lutomirski (14):
wmi: Drop "Mapper (un)loaded" messages
wmi: Pass the acpi_device through to parse_wdg
wmi: Clean up acpi_wmi_add
wmi: Track wmi devices per ACPI device
wmi: Turn WMI into a bus driver
wmi: Fix error handling when creating devices
wmi: Split devices into types and add basic sysfs attributes
wmi: Probe data objects for read and write capabilities
wmi: Instantiate all devices before adding them
wmi: Add a driver .notify function
wmi: Add a new interface to read block data
wmi: Switch from acpi_driver.notify to acpi_install_notify_handler
wmi: Bind the platform device, not the ACPI node
dell-wmi: Convert to the WMI bus infrastructure
drivers/platform/x86/dell-wmi.c | 132 ++++----
drivers/platform/x86/wmi.c | 649 ++++++++++++++++++++++++++++++++--------
include/linux/wmi.h | 58 ++++
3 files changed, 644 insertions(+), 195 deletions(-)
create mode 100644 include/linux/wmi.h
--
2.5.0
next reply other threads:[~2015-12-01 1:05 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-01 1:05 Andy Lutomirski [this message]
2015-12-01 1:05 ` [PATCH 01/14] wmi: Drop "Mapper (un)loaded" messages Andy Lutomirski
2015-12-01 1:05 ` [PATCH 02/14] wmi: Pass the acpi_device through to parse_wdg Andy Lutomirski
2015-12-01 1:05 ` [PATCH 03/14] wmi: Clean up acpi_wmi_add Andy Lutomirski
2015-12-01 1:05 ` [PATCH 04/14] wmi: Track wmi devices per ACPI device Andy Lutomirski
2015-12-01 1:05 ` [PATCH 05/14] wmi: Turn WMI into a bus driver Andy Lutomirski
2016-01-16 12:56 ` Michał Kępień
2016-01-16 16:19 ` Andy Lutomirski
2015-12-01 1:05 ` [PATCH 06/14] wmi: Fix error handling when creating devices Andy Lutomirski
2015-12-01 1:05 ` [PATCH 07/14] wmi: Split devices into types and add basic sysfs attributes Andy Lutomirski
2015-12-01 1:05 ` [PATCH 08/14] wmi: Probe data objects for read and write capabilities Andy Lutomirski
2016-01-16 13:11 ` Michał Kępień
2016-01-16 16:14 ` Andy Lutomirski
2017-01-10 5:56 ` Michał Kępień
2017-01-10 10:05 ` Andy Lutomirski
2017-01-12 5:01 ` Michał Kępień
2017-01-13 1:42 ` Andy Lutomirski
2015-12-01 1:05 ` [PATCH 09/14] wmi: Instantiate all devices before adding them Andy Lutomirski
2016-01-17 14:06 ` Michał Kępień
2015-12-01 1:06 ` [PATCH 10/14] wmi: Add a driver .notify function Andy Lutomirski
2015-12-01 1:06 ` [PATCH 11/14] wmi: Add a new interface to read block data Andy Lutomirski
2015-12-01 1:06 ` [PATCH 12/14] wmi: Switch from acpi_driver.notify to acpi_install_notify_handler Andy Lutomirski
2015-12-01 1:06 ` [PATCH 13/14] wmi: Bind the platform device, not the ACPI node Andy Lutomirski
2015-12-01 1:06 ` [PATCH 14/14] dell-wmi: Convert to the WMI bus infrastructure Andy Lutomirski
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=cover.1448931782.git.luto@kernel.org \
--to=luto@kernel.org \
--cc=dvhart@infradead.org \
--cc=linux-acpi@vger.kernel.org \
--cc=mario_limonciello@dell.com \
--cc=mjg59@srcf.ucam.org \
--cc=pali.rohar@gmail.com \
--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;
as well as URLs for NNTP newsgroup(s).