From mboxrd@z Thu Jan 1 00:00:00 1970 From: Darren Hart 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 Message-ID: <20170606170201.GC32509@fury> References: <20170606100440.GA4690@pali> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit Return-path: Content-Disposition: inline In-Reply-To: <20170606100440.GA4690@pali> Sender: platform-driver-x86-owner@vger.kernel.org To: Pali =?iso-8859-1?Q?Roh=E1r?= Cc: Andy Lutomirski , platform-driver-x86@vger.kernel.org, Andy Shevchenko , Andy Lutomirski , Mario Limonciello , Rafael Wysocki , linux-kernel@vger.kernel.org, linux-acpi@vger.kernel.org List-Id: linux-acpi@vger.kernel.org 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