From: Darren Hart <dvhart@infradead.org>
To: Mattias Jacobsson <2pi@mok.nu>
Cc: andy@infradead.org, mario.limonciello@dell.com,
michal.lkml@markovi.net, mjg59@srcf.ucam.org,
pali.rohar@gmail.com, yamada.masahiro@socionext.com,
platform-driver-x86@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v4 0/8] platform/x86: wmi: add WMI support to
Date: Wed, 6 Mar 2019 22:20:39 -0800 [thread overview]
Message-ID: <20190307062039.GG44339@wrath> (raw)
In-Reply-To: <cover.1550603967.git.2pi@mok.nu>
On Tue, Feb 19, 2019 at 08:59:48PM +0100, Mattias Jacobsson wrote:
> The kernel provides the macro MODULE_DEVICE_TABLE() which can help
> driver authors to generate the appropriate MODULE_ALIAS() output. The
> WMI device type is currently not supported by MODULE_DEVICE_TABLE().
Thanks Mattias. I have this queued up for testing, and with an ack from
Masahiro for 2/8, I'll pull this in. Thanks for the patches.
--
Darren Hart
VMware Open Source Technology Center
prev parent reply other threads:[~2019-03-07 6:20 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-19 19:59 [PATCH v4 0/8] platform/x86: wmi: add WMI support to Mattias Jacobsson
2019-02-19 19:59 ` [PATCH v4 1/8] platform/x86: wmi: move struct wmi_device_id to mod_devicetable.h Mattias Jacobsson
2019-02-19 19:59 ` [PATCH v4 2/8] platform/x86: wmi: add WMI support to MODULE_DEVICE_TABLE() Mattias Jacobsson
2019-02-19 19:59 ` [PATCH v4 3/8] platform/x86: dell-smbios-wmi: use MODULE_DEVICE_TABLE() instead of MODULE_ALIAS() Mattias Jacobsson
2019-02-19 19:59 ` [PATCH v4 4/8] platform/x86: dell-wmi-descriptor: " Mattias Jacobsson
2019-02-19 19:59 ` [PATCH v4 5/8] platform/x86: dell-wmi: " Mattias Jacobsson
2019-02-19 19:59 ` [PATCH v4 6/8] platform/x86: huawei-wmi: " Mattias Jacobsson
2019-02-19 19:59 ` [PATCH v4 7/8] platform/x86: intel-wmi-thunderbolt: " Mattias Jacobsson
2019-02-19 19:59 ` [PATCH v4 8/8] platform/x86: wmi-bmof: " Mattias Jacobsson
2019-03-07 6:20 ` Darren Hart [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=20190307062039.GG44339@wrath \
--to=dvhart@infradead.org \
--cc=2pi@mok.nu \
--cc=andy@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mario.limonciello@dell.com \
--cc=michal.lkml@markovi.net \
--cc=mjg59@srcf.ucam.org \
--cc=pali.rohar@gmail.com \
--cc=platform-driver-x86@vger.kernel.org \
--cc=yamada.masahiro@socionext.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).