linux-pm.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Lee Jones <lee.jones@linaro.org>
To: Matti Vaittinen <matti.vaittinen@fi.rohmeurope.com>
Cc: mazziesaccount@gmail.com,
	Sebastian Reichel <sebastian.reichel@collabora.com>,
	Linus Walleij <linus.walleij@linaro.org>,
	Krzysztof Kozlowski <krzk@kernel.org>,
	Dmitry Osipenko <digetx@gmail.com>,
	Cong Pham <cpham2403@gmail.com>,
	rostokus@gmail.com, fan.chen@mediatek.com,
	linux-kernel@vger.kernel.org, linux-pm@vger.kernel.org
Subject: Re: [RFC PATCH v2 3/6] mfd: prepare to support BD718xx-charger
Date: Wed, 16 Dec 2020 08:49:07 +0000	[thread overview]
Message-ID: <20201216084907.GF4776@dell> (raw)
In-Reply-To: <ebcd976ba60a8cf417787b8b0643f12dcc68cf0a.1607085199.git.matti.vaittinen@fi.rohmeurope.com>

On Fri, 04 Dec 2020, Matti Vaittinen wrote:

> Add definitions for ROHM BD718(27/28/78) PMIC's charger blocks.
> 
> Signed-off-by: Matti Vaittinen <matti.vaittinen@fi.rohmeurope.com>
> ---
> 
> This patch was not in v1. This brings in some charger registers
> for the BD71828 charger driver which is in following patches. Patch
> split here reflects the subsystem change (for non RFC submitted for
> inclusion this would probably be Lee's territory). Now provided in
> this RFC series to give more context
> 
>  include/linux/mfd/rohm-bd71828.h | 65 ++++++++++++++++++++++++++++++++
>  include/linux/mfd/rohm-generic.h |  2 +
>  2 files changed, 67 insertions(+)

For my own reference (apply this as-is to your sign-off block):

  Acked-for-MFD-by: Lee Jones <lee.jones@linaro.org>

-- 
Lee Jones [李琼斯]
Senior Technical Lead - Developer Services
Linaro.org │ Open source software for Arm SoCs
Follow Linaro: Facebook | Twitter | Blog

  reply	other threads:[~2020-12-16  8:49 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-12-04 12:39 [RFC PATCH v2 0/6] power: supply: Add some fuel-gauge logic Matti Vaittinen
2020-12-04 12:41 ` [RFC PATCH v2 1/6] power: supply: add cap2ocv batinfo helper Matti Vaittinen
2020-12-08  8:54   ` Linus Walleij
2020-12-08  9:30     ` Vaittinen, Matti
2020-12-04 12:43 ` [RFC PATCH v2 2/6] power: supply: add sw-gauge for SOC estimation and CC correction Matti Vaittinen
2020-12-04 12:47 ` [RFC PATCH v2 3/6] mfd: prepare to support BD718xx-charger Matti Vaittinen
2020-12-16  8:49   ` Lee Jones [this message]
2020-12-04 12:49 ` [RFC PATCH v2 4/6] mfd: add BD71827 header Matti Vaittinen
2020-12-16  8:53   ` Lee Jones
2020-12-17  9:40     ` Vaittinen, Matti
2020-12-04 12:53 ` [RFC PATCH v2 5/6] power: supply: Add bd718(27/28/78) charger driver Matti Vaittinen
2020-12-04 12:54 ` [RFC PATCH v2 6/6] MFD: bd71828: differentiate bd71828 and bd71827 chargers Matti Vaittinen
2020-12-16  8:55   ` Lee Jones

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=20201216084907.GF4776@dell \
    --to=lee.jones@linaro.org \
    --cc=cpham2403@gmail.com \
    --cc=digetx@gmail.com \
    --cc=fan.chen@mediatek.com \
    --cc=krzk@kernel.org \
    --cc=linus.walleij@linaro.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pm@vger.kernel.org \
    --cc=matti.vaittinen@fi.rohmeurope.com \
    --cc=mazziesaccount@gmail.com \
    --cc=rostokus@gmail.com \
    --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).