From: Darren Hart <dvhart@infradead.org>
To: "Ognjen Galić" <smclt30p@gmail.com>
Cc: "Rafael J. Wysocki" <rafael@kernel.org>,
"Rafael J. Wysocki" <rjw@rjwysocki.net>,
Len Brown <lenb@kernel.org>,
Robert Moore <robert.moore@intel.com>,
Lv Zheng <lv.zheng@intel.com>,
ACPI Devel Maling List <linux-acpi@vger.kernel.org>,
devel@acpica.org, Andy Shevchenko <andy@infradead.org>,
Henrique de Moraes Holschuh <ibm-acpi@hmh.eng.br>,
Sebastian Reichel <sre@kernel.org>,
Platform Driver <platform-driver-x86@vger.kernel.org>,
ibm-acpi-devel@lists.sourceforge.net,
Linux PM <linux-pm@vger.kernel.org>
Subject: Re: [PATCH 1/3 v6] battery: Add the battery hooking API
Date: Wed, 20 Dec 2017 13:17:19 -0800 [thread overview]
Message-ID: <20171220211617.GA14667@fury> (raw)
In-Reply-To: <CALgTWSuWoj6ecfNZmpn68uGV4m+Rz2adAWrw-Ng-7rU75SVtHQ@mail.gmail.com>
On Wed, Dec 20, 2017 at 03:30:18PM +0100, Ognjen Galić wrote:
> On 18/12/2017, Rafael J. Wysocki <rafael@kernel.org> 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
next prev parent reply other threads:[~2017-12-20 21:17 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-15 16:56 [PATCH 1/3 v6] battery: Add the battery hooking API Ognjen Galic
2017-12-18 18:04 ` [Devel] " Rafael J. Wysocki
2017-12-18 18:04 ` Rafael J. Wysocki
2017-12-20 14:30 ` Ognjen Galić
2017-12-20 21:17 ` Darren Hart [this message]
2017-12-20 21:23 ` Ognjen Galić
[not found] ` <CALgTWSvEg3EfjSJqAp5nRuxRceBpg92=x3FPFEW9PThBmizQEA-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2017-12-20 21:58 ` Darren Hart
2017-12-20 19:32 ` Ognjen Galic
2017-12-20 19:42 ` Ognjen Galić
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=20171220211617.GA14667@fury \
--to=dvhart@infradead.org \
--cc=andy@infradead.org \
--cc=devel@acpica.org \
--cc=ibm-acpi-devel@lists.sourceforge.net \
--cc=ibm-acpi@hmh.eng.br \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=lv.zheng@intel.com \
--cc=platform-driver-x86@vger.kernel.org \
--cc=rafael@kernel.org \
--cc=rjw@rjwysocki.net \
--cc=robert.moore@intel.com \
--cc=smclt30p@gmail.com \
--cc=sre@kernel.org \
/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.