From mboxrd@z Thu Jan 1 00:00:00 1970 From: Darren Hart Subject: Re: [PATCH 1/3 v6] battery: Add the battery hooking API Date: Wed, 20 Dec 2017 13:17:19 -0800 Message-ID: <20171220211617.GA14667@fury> References: <20171215165654.GA6209@thinkpad> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit Return-path: Content-Disposition: inline In-Reply-To: Sender: linux-acpi-owner@vger.kernel.org To: Ognjen =?utf-8?B?R2FsacSH?= Cc: "Rafael J. Wysocki" , "Rafael J. Wysocki" , Len Brown , Robert Moore , Lv Zheng , ACPI Devel Maling List , devel@acpica.org, Andy Shevchenko , Henrique de Moraes Holschuh , Sebastian Reichel , Platform Driver , ibm-acpi-devel@lists.sourceforge.net, Linux PM List-Id: linux-pm@vger.kernel.org On Wed, Dec 20, 2017 at 03:30:18PM +0100, Ognjen Galić wrote: > On 18/12/2017, Rafael J. Wysocki wrote: > > Also, what if someone attempts to add a hook when the ACPI battery > > module is not loaded? Will that still work? > > The module that requests the hooks will fail to load with the following > > > [ 149.259127] thinkpad_acpi: Unknown symbol battery_hook_register (err 0) > > [ 149.259158] thinkpad_acpi: Unknown symbol battery_hook_unregister (err 0) Will a synchronous request_module() address this concern? -- Darren Hart VMware Open Source Technology Center