From: Vladimir Barinov <vladimir.barinov@cogentembedded.com>
To: dbaryshkov@gmail.com
Cc: "anton@enomsg.org" <anton@enomsg.org>,
dwmw2@infradead.org, linux-kernel@vger.kernel.org,
devicetree@vger.kernel.org, mk7.kang@samsung.com,
k.kozlowski@samsung.com, mark.rutland@arm.com
Subject: Re: [PATCH v2 0/3] power_supply: modelgauge_battery: Add Maxim ModelGauge ICs gauge
Date: Wed, 26 Feb 2014 14:21:07 +0400 [thread overview]
Message-ID: <530DC013.9040908@cogentembedded.com> (raw)
In-Reply-To: <1391293385-27539-1-git-send-email-vladimir.barinov@cogentembedded.com>
Hello Dmitry,
In accordance to this change you've taken the responsibility for power
supply maintainership.
https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/MAINTAINERS?id=573189354b7c97cd2256b87cf083ee435584594e
It passed almost month and no answer from you.
Does it make sense to apply this patch series?
Regards,
Vladimir
On 02/02/2014 02:23 AM, Vladimir Barinov wrote:
> Hello.
>
> This adds the folowing:
> - Maxim ModelGauge ICs gauge driver for MAX17040/41/43/44/48/49/58/59 chips
> - Document DT bindings
> - Remove superseded Maxim MAX17040 gauge driver
>
> Vladimir Barinov (3):
> [1/3] power_supply: modelgauge_battery: Maxim ModelGauge ICs gauge
> [2/3] dt: Document ModelGauge gauge bindings
> [3/3] power_supply: modelgauge_battery: Remove Maxim MAX17040 gauge
>
> ---
> This patchset is against the 'kernel/git/torvalds/linux.git' repo.
>
> Changes since v1:
> - switched to REGMAP API
> - replaced request_threaded_irq with devm_request_threaded_irq
> - replaced cancel_delayed_work with _sync version
> - moved "empty_alert_threshold, soc_change_alert, hibernate_threshold,
> active_threshold, undervoltage, overvoltage, resetvoltage" parameters
> out from platform_data and DT
> - removed unused parameters "empty_adjustment, empty_adjustment"
> - added return value checks for of_property_read_XX functions
> - removed irrelevant bindings
> - fixed dt properties naming in documentation
> - added binding size description in documentation
> - removed satelite include file include/linux/max17040_battery.h
>
> Documentation/devicetree/bindings/power_supply/modelgauge_battery.txt | 61
> drivers/power/Kconfig | 17
> drivers/power/Makefile | 2
> drivers/power/max17040_battery.c | 297 ---
> drivers/power/modelgauge_battery.c | 838 ++++++++++
> include/linux/max17040_battery.h | 19
> include/linux/platform_data/battery-modelgauge.h | 31
> 7 files changed, 940 insertions(+), 325 deletions(-)
prev parent reply other threads:[~2014-02-26 10:21 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-01 22:23 [PATCH v2 0/3] power_supply: modelgauge_battery: Add Maxim ModelGauge ICs gauge Vladimir Barinov
2014-02-01 22:23 ` [PATCH v2 1/3] power_supply: modelgauge_battery: " Vladimir Barinov
2014-03-04 10:48 ` Krzysztof Kozlowski
2014-03-04 12:05 ` Krzysztof Kozlowski
2014-02-01 22:23 ` [PATCH v2 2/3] dt: Document ModelGauge gauge bindings Vladimir Barinov
2014-02-01 22:23 ` [PATCH v2 3/3] power_supply: modelgauge_battery: Remove Maxim MAX17040 gauge Vladimir Barinov
2014-02-26 10:21 ` Vladimir Barinov [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=530DC013.9040908@cogentembedded.com \
--to=vladimir.barinov@cogentembedded.com \
--cc=anton@enomsg.org \
--cc=dbaryshkov@gmail.com \
--cc=devicetree@vger.kernel.org \
--cc=dwmw2@infradead.org \
--cc=k.kozlowski@samsung.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=mk7.kang@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).