From: Lee Jones <lee.jones@linaro.org>
To: Sven Van Asbroeck <thesven73@gmail.com>
Cc: Pavel Machek <pavel@ucw.cz>,
Linus Walleij <linus.walleij@linaro.org>,
Grigoryev Denis <grigoryev@fastwel.ru>,
Axel Lin <axel.lin@ingics.com>,
Jacek Anaszewski <jacek.anaszewski@gmail.com>,
Dan Murphy <dmurphy@ti.com>, Rob Herring <robh+dt@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-leds@vger.kernel.org
Subject: Re: [PATCH v6 2/2] dt-bindings: mfd: update TI tps6105x chip bindings
Date: Mon, 16 Dec 2019 16:38:02 +0000 [thread overview]
Message-ID: <20191216163802.GA18955@dell> (raw)
In-Reply-To: <20191216143259.24587-3-TheSven73@gmail.com>
On Mon, 16 Dec 2019, Sven Van Asbroeck wrote:
> The driver has been extended to optionally get its operational
> mode, regulator init data and LED naming from the devicetree.
>
> Acked-by: Jacek Anaszewski <jacek.anaszewski@gmail.com>
> Reviewed-by: Rob Herring <robh@kernel.org>
> Signed-off-by: Sven Van Asbroeck <TheSven73@gmail.com>
> ---
> .../devicetree/bindings/mfd/tps6105x.txt | 47 ++++++++++++++++++-
> 1 file changed, 46 insertions(+), 1 deletion(-)
For my own reference:
Acked-for-MFD-by: Lee Jones <lee.jones@linaro.org>
--
Lee Jones [李琼斯]
Linaro Services Technical Lead
Linaro.org │ Open source software for ARM SoCs
Follow Linaro: Facebook | Twitter | Blog
prev parent reply other threads:[~2019-12-16 16:38 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-16 14:32 [PATCH v6 0/2] tps6105x add devicetree and leds support Sven Van Asbroeck
2019-12-16 14:32 ` [PATCH v6 1/2] leds: tps6105x: add driver for MFD chip LED mode Sven Van Asbroeck
2019-12-21 19:04 ` Pavel Machek
2019-12-16 14:32 ` [PATCH v6 2/2] dt-bindings: mfd: update TI tps6105x chip bindings Sven Van Asbroeck
2019-12-16 16:38 ` Lee Jones [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=20191216163802.GA18955@dell \
--to=lee.jones@linaro.org \
--cc=axel.lin@ingics.com \
--cc=devicetree@vger.kernel.org \
--cc=dmurphy@ti.com \
--cc=grigoryev@fastwel.ru \
--cc=jacek.anaszewski@gmail.com \
--cc=linus.walleij@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-leds@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=pavel@ucw.cz \
--cc=robh+dt@kernel.org \
--cc=thesven73@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.