[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAHp75Vc0umEt0cGn5-NWva6j1T0yry1Ag7Egnn4iSvz=cs_kTg@mail.gmail.com>
Date: Thu, 5 Oct 2017 08:29:10 +0300
From: Andy Shevchenko <andy.shevchenko@...il.com>
To: Darren Hart <dvhart@...radead.org>
Cc: Mario Limonciello <mario.limonciello@...l.com>,
LKML <linux-kernel@...r.kernel.org>,
Platform Driver <platform-driver-x86@...r.kernel.org>,
Andy Lutomirski <luto@...nel.org>, quasisec@...gle.com,
Pali Rohár <pali.rohar@...il.com>,
"Rafael J. Wysocki" <rjw@...ysocki.net>, mjg59@...gle.com,
Christoph Hellwig <hch@....de>, Greg KH <greg@...ah.com>
Subject: Re: [PATCH v4 05/14] platform/x86: dell-wmi-descriptor: split WMI
descriptor into it's own driver
On Thu, Oct 5, 2017 at 4:09 AM, Darren Hart <dvhart@...radead.org> wrote:
> On Wed, Oct 04, 2017 at 05:48:31PM -0500, Mario Limonciello wrote:
>> All communication on individual GUIDs should occur in separate drivers.
>> Allowing a driver to communicate with the bus to another GUID is just
>> a hack that discourages drivers to adopt the bus model.
>>
>> The information found from the WMI descriptor driver is now exported
>> for use by other drivers.
> You'll want to add something like:
>
> #ifdef CONFIG_DELL_WMI_DESCRIPTOR_MODULE
> if (request_module("dell_wmi_descriptor"))
> /* FAIL */
> #endif
>
> During init.
I don't think #ifdef is needed.
We may just request module.
But looking in the code it seems that we simple need to select that
module. No request_module will be needed.
Did I miss something?
--
With Best Regards,
Andy Shevchenko
Powered by blists - more mailing lists