From: Jenny Tc <jenny.tc@intel.com>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: "Pali Rohár" <pali.rohar@gmail.com>,
linux-kernel@vger.kernel.org,
"Anton Vorontsov" <anton@enomsg.org>,
luca@coelho.fi, "Johannes Berg" <johannes.berg@intel.com>
Subject: Re: [PATCH 3.14] power_supply: don't export power_supply_notifier
Date: Tue, 25 Feb 2014 17:07:53 +0530 [thread overview]
Message-ID: <20140225113753.GA20856@jenny-desktop> (raw)
In-Reply-To: <1392988768-16693-1-git-send-email-johannes@sipsolutions.net>
On Fri, Feb 21, 2014 at 02:19:28PM +0100, Johannes Berg wrote:
> From: Johannes Berg <johannes.berg@intel.com>
>
> Since there are registration/unregistration functions and the
> invocation is in the core code, there's no need to export the
> notifier chain head, make it static instead.
This is a generic notifier which can be used outside power_supply_core.c
to post psy events as in patch
power_supply-Introduce-generic-psy-charging-driver.patch. So the notifier chain
need to be exported.
prev parent reply other threads:[~2014-02-25 11:37 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-21 13:19 Johannes Berg
2014-02-25 11:37 ` Jenny Tc [this message]
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=20140225113753.GA20856@jenny-desktop \
--to=jenny.tc@intel.com \
--cc=anton@enomsg.org \
--cc=johannes.berg@intel.com \
--cc=johannes@sipsolutions.net \
--cc=linux-kernel@vger.kernel.org \
--cc=luca@coelho.fi \
--cc=pali.rohar@gmail.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®