From: Sebastian Reichel <sre@kernel.org>
To: Srikant Ritolia <s.ritolia@samsung.com>
Cc: linux-pm@vger.kernel.org, vidushi.koul@samsung.com,
srikant.ritolia@gmail.com
Subject: Re: [PATCH] power: max8997_charger: Using device managed API and remove OOM print
Date: Sat, 17 Dec 2016 17:09:38 +0100 [thread overview]
Message-ID: <20161217160937.sbki4hs6ba7erbuf@earth> (raw)
In-Reply-To: <1481188357-11889-1-git-send-email-s.ritolia@samsung.com>
[-- Attachment #1: Type: text/plain, Size: 834 bytes --]
Hi,
On Thu, Dec 08, 2016 at 02:42:37PM +0530, Srikant Ritolia wrote:
> Use managed resource function devm_power_supply_register instead of
> power_supply_register to simplify the error path by allowing unregistering
> to happen automatically on error and remove.
> Removing max8997_battery_remove function also as it is now redundant.
>
> Also removing out of memory printk message after kzalloc as there is
> already enough information on failure.
>
> Signed-off-by: Srikant Ritolia <s.ritolia@samsung.com>
Thanks for your patch. We are currently in the merge
window and your patch will appear in linux-next once
4.10-rc1 has been tagged by Linus Torvalds.
Until then I queued it into this branch:
https://git.kernel.org/cgit/linux/kernel/git/sre/linux-power-supply.git/log/?h=for-next-next
-- Sebastian
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
prev parent reply other threads:[~2016-12-17 16:09 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-08 9:12 [PATCH] power: max8997_charger: Using device managed API and remove OOM print Srikant Ritolia
2016-12-17 16:09 ` Sebastian Reichel [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=20161217160937.sbki4hs6ba7erbuf@earth \
--to=sre@kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=s.ritolia@samsung.com \
--cc=srikant.ritolia@gmail.com \
--cc=vidushi.koul@samsung.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;
as well as URLs for NNTP newsgroup(s).