From: Darren Hart <dvhart@infradead.org>
To: "Pali Rohár" <pali.rohar@gmail.com>
Cc: Andy Lutomirski <luto@kernel.org>,
platform-driver-x86@vger.kernel.org,
Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
Andy Lutomirski <luto@amacapital.net>,
Mario Limonciello <mario_limonciello@dell.com>,
Rafael Wysocki <rjw@rjwysocki.net>,
linux-kernel@vger.kernel.org, linux-acpi@vger.kernel.org
Subject: Re: [PATCH v2] platform/x86: wmi-bmof: New driver to expose embedded Binary WMI MOF metadata
Date: Tue, 6 Jun 2017 10:02:01 -0700 [thread overview]
Message-ID: <20170606170201.GC32509@fury> (raw)
In-Reply-To: <20170606100440.GA4690@pali>
On Tue, Jun 06, 2017 at 12:04:40PM +0200, Pali Rohár wrote:
> On Monday 05 June 2017 20:16:44 Andy Lutomirski wrote:
> > +#define WMI_BMOF_GUID "05901221-D566-11D1-B2F0-00A0C9062910"
> > +MODULE_ALIAS("wmi:" WMI_BMOF_GUID);
>
> Cannot we generate MODULE_ALIAS from module_wmi_driver()? IIRC it is
> working for i2c drivers.
I could see this being automated since we always use wmi:GUID, but it isn't
currently. Happy to consider it as a follow on.
Do you have a specific i2c example you think we should consider following?
--
Darren Hart
VMware Open Source Technology Center
next prev parent reply other threads:[~2017-06-06 17:02 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-06 3:16 [PATCH v2] platform/x86: wmi-bmof: New driver to expose embedded Binary WMI MOF metadata Andy Lutomirski
2017-06-06 9:30 ` Andy Shevchenko
2017-06-06 16:34 ` Darren Hart
2017-06-06 16:54 ` Darren Hart
2017-06-06 18:45 ` Andy Shevchenko
2017-06-06 10:04 ` Pali Rohár
2017-06-06 17:02 ` Darren Hart [this message]
2017-06-06 20:50 ` Pali Rohár
2017-07-04 13:28 ` Pali Rohár
2017-11-23 14:39 ` Pali Rohár
2017-11-23 14:48 ` Andy Lutomirski
2017-06-06 22:31 ` Andy Lutomirski
2017-06-06 23:35 ` kbuild test robot
2017-06-06 23:35 ` kbuild test robot
2017-06-19 16:07 ` Pali Rohár
2017-06-19 16:13 ` Mario.Limonciello
2017-06-19 16:13 ` Mario.Limonciello
2017-06-19 16:19 ` Pali Rohár
2017-06-19 16:23 ` Andy Lutomirski
2017-06-20 12:12 ` Pali Rohár
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=20170606170201.GC32509@fury \
--to=dvhart@infradead.org \
--cc=andriy.shevchenko@linux.intel.com \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luto@amacapital.net \
--cc=luto@kernel.org \
--cc=mario_limonciello@dell.com \
--cc=pali.rohar@gmail.com \
--cc=platform-driver-x86@vger.kernel.org \
--cc=rjw@rjwysocki.net \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.