From: Dmitry Osipenko <digetx@gmail.com>
To: Sebastian Reichel <sebastian.reichel@collabora.com>,
Sebastian Reichel <sre@kernel.org>
Cc: linux-pm@vger.kernel.org, linux-kernel@vger.kernel.org,
kernel@collabora.com
Subject: Re: [PATCHv1 0/2] power: supply: smb347-charger: Cleanups
Date: Fri, 28 Aug 2020 10:47:21 +0300 [thread overview]
Message-ID: <4d02de0e-7345-a937-7fce-66f4438a8144@gmail.com> (raw)
In-Reply-To: <20200826144159.353837-1-sebastian.reichel@collabora.com>
26.08.2020 17:41, Sebastian Reichel пишет:
> Hi Dmitry,
>
> Please check the following cleanup patches for smb347 driver
> do not break functionality on your Nexus 7.
>
> -- Sebastian
>
> Sebastian Reichel (2):
> power: supply: smb347-charger: Drop pdata support
> power: supply: smb347-charger: Use generic property framework
>
> drivers/power/supply/smb347-charger.c | 305 ++++++++++++++------------
> include/linux/power/smb347-charger.h | 114 ----------
> 2 files changed, 167 insertions(+), 252 deletions(-)
> delete mode 100644 include/linux/power/smb347-charger.h
>
Hello, Sebastian!
Thank you very much, very nice cleanup! I checked that the DT properties
are applied correctly and everything works properly on Nexus 7 after
applying this series just like it worked before, no problems spotted,
charger does its job and battery is charging up fine!
next prev parent reply other threads:[~2020-08-28 7:47 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-26 14:41 [PATCHv1 0/2] power: supply: smb347-charger: Cleanups Sebastian Reichel
2020-08-26 14:41 ` [PATCHv1 1/2] power: supply: smb347-charger: Drop pdata support Sebastian Reichel
2020-08-28 7:47 ` Dmitry Osipenko
2020-08-26 14:41 ` [PATCHv1 2/2] power: supply: smb347-charger: Use generic property framework Sebastian Reichel
2020-08-28 7:47 ` Dmitry Osipenko
2020-08-28 7:47 ` Dmitry Osipenko [this message]
2020-08-28 15:06 ` [PATCHv1 0/2] power: supply: smb347-charger: Cleanups 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=4d02de0e-7345-a937-7fce-66f4438a8144@gmail.com \
--to=digetx@gmail.com \
--cc=kernel@collabora.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=sebastian.reichel@collabora.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;
as well as URLs for NNTP newsgroup(s).