From: Krzysztof Kozlowski <k.kozlowski@samsung.com>
To: Sebastian Reichel <sre@kernel.org>,
Dmitry Eremin-Solenikov <dbaryshkov@gmail.com>,
David Woodhouse <dwmw2@infradead.org>,
Krzysztof Kozlowski <k.kozlowski@samsung.com>,
Myungjoo Ham <myungjoo.ham@samsung.com>,
Anton Vorontsov <anton@enomsg.org>,
Jonghwa Lee <jonghwa3.lee@samsung.com>,
linux-pm@vger.kernel.org, linux-kernel@vger.kernel.org
Cc: Chanwoo Choi <cw00.choi@samsung.com>,
Kyungmin Park <kyungmin.park@samsung.com>,
Marek Szyprowski <m.szyprowski@samsung.com>,
Bartlomiej Zolnierkiewicz <b.zolnierkie@samsung.com>
Subject: [PATCH 0/2] power: charger-manager: Fixes for unbinding other psy
Date: Mon, 13 Oct 2014 15:34:29 +0200 [thread overview]
Message-ID: <1413207271-23836-1-git-send-email-k.kozlowski@samsung.com> (raw)
Hi,
These are two fixes for accessing old power supply by charger manager
after unbinding the driver implementing given power supply.
Actually the source of these two bugs and the solution for them is the
same in both patches. However I decided to split this because fixing
this was quite intrusive and squashed patch would be rather big.
Best regards,
Krzysztof
Krzysztof Kozlowski (2):
power: charger-manager: Fix accessing invalidated power supply after
fuel gauge unbind
power: charger-manager: Fix accessing invalidated power supply after
charger unbind
drivers/power/charger-manager.c | 161 +++++++++++++++++++++++-----------
include/linux/power/charger-manager.h | 3 -
2 files changed, 108 insertions(+), 56 deletions(-)
--
1.9.1
next reply other threads:[~2014-10-13 13:34 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-13 13:34 Krzysztof Kozlowski [this message]
2014-10-13 13:34 ` [PATCH 1/2] power: charger-manager: Fix accessing invalidated power supply after fuel gauge unbind Krzysztof Kozlowski
2014-10-13 13:34 ` [PATCH 2/2] power: charger-manager: Fix accessing invalidated power supply after charger unbind Krzysztof Kozlowski
2014-10-27 18:43 ` [PATCH 0/2] power: charger-manager: Fixes for unbinding other psy Sebastian Reichel
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=1413207271-23836-1-git-send-email-k.kozlowski@samsung.com \
--to=k.kozlowski@samsung.com \
--cc=anton@enomsg.org \
--cc=b.zolnierkie@samsung.com \
--cc=cw00.choi@samsung.com \
--cc=dbaryshkov@gmail.com \
--cc=dwmw2@infradead.org \
--cc=jonghwa3.lee@samsung.com \
--cc=kyungmin.park@samsung.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=m.szyprowski@samsung.com \
--cc=myungjoo.ham@samsung.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox