From: Viresh Kumar <viresh.kumar@linaro.org>
To: sre@kernel.org, dbaryshkov@gmail.com, dwmw2@infradead.org,
anton@enomsg.org
Cc: linux-pm@vger.kernel.org, linaro-kernel@lists.linaro.org,
Viresh Kumar <viresh.kumar@linaro.org>
Subject: [PATCH 00/15] power_supply: Fixes & cleanups
Date: Thu, 4 Sep 2014 17:30:04 +0530 [thread overview]
Message-ID: <cover.1409831636.git.viresh.kumar@linaro.org> (raw)
Hi Guys,
I was required to work on a battery driver and found some fixes/cleanups while
going through the core.
First two are fixes and rest are cleanups. Please see if they make any sense at
all.
Pushed here: git://git.kernel.org/pub/scm/linux/kernel/git/vireshk/linux.git battery/fixes
--
viresh
Viresh Kumar (15):
power-supply: Don't over-allocate memory for "supplied-from" array
power-supply: Return early if "power-supplies" property isn't valid
Documentation: Charger Manager: Fix spelling mistakes
power-supply: Forward declare structs together
power-supply: Drop unnecessary typecasts
power-supply: Use 'break' instead of 'continue' to end loop
power-supply: Rearrange code to remove duplicate lines
power-supply: Propagate error returned by
power_supply_find_supply_from_node()
power-supply: Don't return -EINVAL from
__power_supply_find_supply_from_node()
power-supply: Drop useless 'if (ret.intval)' statements
power-supply: Mark 'if' blocks in power_supply_changed_work() with
'likely'
power-supply: Use PTR_ERR_OR_ZERO() routine
power-supply: Check for failures only when we can fail
power-supply: Avoid unnecessary 'goto' statements
power_supply: Don't iterate over devices to return -EPROBE_DEFER
Documentation/power/charger-manager.txt | 2 +-
drivers/power/power_supply_core.c | 100 +++++++++++++++-----------------
drivers/power/power_supply_leds.c | 19 ++----
drivers/power/power_supply_sysfs.c | 21 +++----
include/linux/power_supply.h | 3 +-
5 files changed, 64 insertions(+), 81 deletions(-)
--
2.0.3.693.g996b0fd
next reply other threads:[~2014-09-04 12:00 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-04 12:00 Viresh Kumar [this message]
2014-09-04 12:01 ` [PATCH 01/15] power-supply: Don't over-allocate memory for "supplied-from" array Viresh Kumar
2014-09-04 12:01 ` [PATCH 02/15] power-supply: Return early if "power-supplies" property isn't valid Viresh Kumar
2014-09-04 12:01 ` [PATCH 03/15] Documentation: Charger Manager: Fix spelling mistakes Viresh Kumar
2014-09-04 12:01 ` [PATCH 04/15] power-supply: Forward declare structs together Viresh Kumar
2014-09-04 12:01 ` [PATCH 05/15] power-supply: Drop unnecessary typecasts Viresh Kumar
2014-09-04 12:01 ` [PATCH 06/15] power-supply: Use 'break' instead of 'continue' to end loop Viresh Kumar
2014-09-04 12:01 ` [PATCH 07/15] power-supply: Rearrange code to remove duplicate lines Viresh Kumar
2014-09-04 12:01 ` [PATCH 08/15] power-supply: Propagate error returned by power_supply_find_supply_from_node() Viresh Kumar
2014-09-04 12:01 ` [PATCH 09/15] power-supply: Don't return -EINVAL from __power_supply_find_supply_from_node() Viresh Kumar
2014-09-04 12:01 ` [PATCH 10/15] power-supply: Drop useless 'if (ret.intval)' statements Viresh Kumar
2014-09-04 12:01 ` [PATCH 11/15] power-supply: Mark 'if' blocks in power_supply_changed_work() with 'likely' Viresh Kumar
2014-09-04 12:01 ` [PATCH 12/15] power-supply: Use PTR_ERR_OR_ZERO() routine Viresh Kumar
2014-09-04 12:01 ` [PATCH 13/15] power-supply: Check for failures only when we can fail Viresh Kumar
2014-09-04 12:01 ` [PATCH 14/15] power-supply: Avoid unnecessary 'goto' statements Viresh Kumar
2014-09-04 12:01 ` [PATCH 15/15] power_supply: Don't iterate over devices to return -EPROBE_DEFER Viresh Kumar
2014-10-01 3:19 ` [PATCH 00/15] power_supply: Fixes & cleanups Viresh Kumar
2014-10-01 15:08 ` Sebastian Reichel
2014-10-02 5:26 ` Viresh Kumar
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=cover.1409831636.git.viresh.kumar@linaro.org \
--to=viresh.kumar@linaro.org \
--cc=anton@enomsg.org \
--cc=dbaryshkov@gmail.com \
--cc=dwmw2@infradead.org \
--cc=linaro-kernel@lists.linaro.org \
--cc=linux-pm@vger.kernel.org \
--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.