From: Angus Ainslie <angus@akkea.ca>
To: Sebastian Reichel <sebastian.reichel@collabora.com>
Cc: krzk@kernel.org, Rob Herring <robh@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
kernel@puri.sm
Subject: Re: [PATCH v2 0/2] Add MAX17055 fuel guage
Date: Thu, 19 Dec 2019 13:18:02 -0800 [thread overview]
Message-ID: <cb3c9effe0995d2cd7b48ef4a9c6ae03@akkea.ca> (raw)
In-Reply-To: <20191219001531.gnav4roprttdwknc@earth.universe>
On 2019-12-18 16:15, Sebastian Reichel wrote:
> Hi,
>
> On Sat, Dec 14, 2019 at 07:27:53AM -0800, Angus Ainslie (Purism) wrote:
>> Extend the max17042_battery driver to include the MAX17055.
>
> Thanks, queued to power-suply's for-next branch.
>
> -- Sebastian
>
Thanks
Angus
>>
>> Changes since v1:
>>
>> Change blacklist driver checks to whitelists.
>>
>> Angus Ainslie (Purism) (2):
>> power: supply: max17042: add MAX17055 support
>> device-tree: bindings: max17042_battery: add all of the compatible
>> strings
>>
>> .../power/supply/max17042_battery.txt | 6 ++-
>> drivers/power/supply/max17042_battery.c | 17 +++++--
>> include/linux/power/max17042_battery.h | 48
>> ++++++++++++++++++-
>> 3 files changed, 66 insertions(+), 5 deletions(-)
>>
>> --
>> 2.17.1
>>
prev parent reply other threads:[~2019-12-19 21:18 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-14 15:27 [PATCH v2 0/2] Add MAX17055 fuel guage Angus Ainslie (Purism)
2019-12-14 15:27 ` [PATCH v2 1/2] power: supply: max17042: add MAX17055 support Angus Ainslie (Purism)
2019-12-17 12:42 ` Krzysztof Kozlowski
2019-12-14 15:27 ` [PATCH v2 2/2] device-tree: bindings: max17042_battery: add all of the compatible strings Angus Ainslie (Purism)
2019-12-19 0:15 ` [PATCH v2 0/2] Add MAX17055 fuel guage Sebastian Reichel
2019-12-19 21:18 ` Angus Ainslie [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=cb3c9effe0995d2cd7b48ef4a9c6ae03@akkea.ca \
--to=angus@akkea.ca \
--cc=devicetree@vger.kernel.org \
--cc=kernel@puri.sm \
--cc=krzk@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=robh@kernel.org \
--cc=sebastian.reichel@collabora.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).