From: Jacek Anaszewski <jacek.anaszewski@gmail.com>
To: Dan Murphy <dmurphy@ti.com>, pavel@ucw.cz
Cc: lee.jones@linaro.org, rdunlap@infradead.org,
linux-leds@vger.kernel.org, linux-kernel@vger.kernel.org,
Liam Girdwood <lgirdwood@gmail.com>,
Mark Brown <broonie@kernel.org>
Subject: Re: [PATCH v4 0/6] LM36274 Introduction
Date: Tue, 14 May 2019 21:11:29 +0200 [thread overview]
Message-ID: <aface058-d34c-9ae0-838d-7e8b0cfe6e10@gmail.com> (raw)
In-Reply-To: <20190507201159.13940-1-dmurphy@ti.com>
I need acks from regulator framework maintainer for patches
1/6 and 4/6.
Adding Liam and Mark.
On 5/7/19 10:11 PM, Dan Murphy wrote:
> Hello
>
> This is patch set v4 for the LM36274. There were no changes made
> to this patch set except to rebase this on top of the latest TI LMU common code
> patchset.
>
> This patch set was rebased on the series at:
> https://lore.kernel.org/patchwork/project/lkml/list/?series=393071
>
> Dan
>
> Dan Murphy (6):
> regulator: lm363x: Make the gpio register enable flexible
> dt-bindings: mfd: Add lm36274 bindings to ti-lmu
> mfd: ti-lmu: Add LM36274 support to the ti-lmu
> regulator: lm363x: Add support for LM36274
> dt-bindings: leds: Add LED bindings for the LM36274
> leds: lm36274: Introduce the TI LM36274 LED driver
>
> .../devicetree/bindings/leds/leds-lm36274.txt | 82 +++++++++
> .../devicetree/bindings/mfd/ti-lmu.txt | 54 ++++++
> drivers/leds/Kconfig | 7 +
> drivers/leds/Makefile | 1 +
> drivers/leds/leds-lm36274.c | 174 ++++++++++++++++++
> drivers/mfd/Kconfig | 5 +-
> drivers/mfd/ti-lmu.c | 14 ++
> drivers/regulator/Kconfig | 2 +-
> drivers/regulator/lm363x-regulator.c | 56 +++++-
> include/linux/mfd/ti-lmu-register.h | 23 +++
> include/linux/mfd/ti-lmu.h | 4 +
> 11 files changed, 416 insertions(+), 6 deletions(-)
> create mode 100644 Documentation/devicetree/bindings/leds/leds-lm36274.txt
> create mode 100644 drivers/leds/leds-lm36274.c
>
--
Best regards,
Jacek Anaszewski
next prev parent reply other threads:[~2019-05-14 19:11 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-07 20:11 [PATCH v4 0/6] LM36274 Introduction Dan Murphy
2019-05-07 20:11 ` [PATCH v4 1/6] regulator: lm363x: Make the gpio register enable flexible Dan Murphy
2019-05-07 20:11 ` [PATCH v4 2/6] dt-bindings: mfd: Add lm36274 bindings to ti-lmu Dan Murphy
2019-05-08 11:52 ` Lee Jones
2019-05-07 20:11 ` [PATCH v4 3/6] mfd: ti-lmu: Add LM36274 support to the ti-lmu Dan Murphy
2019-05-08 11:53 ` Lee Jones
2019-05-07 20:11 ` [PATCH v4 4/6] regulator: lm363x: Add support for LM36274 Dan Murphy
2019-05-07 20:11 ` [PATCH v4 5/6] dt-bindings: leds: Add LED bindings for the LM36274 Dan Murphy
2019-05-07 20:11 ` [PATCH v4 6/6] leds: lm36274: Introduce the TI LM36274 LED driver Dan Murphy
2019-05-20 19:54 ` Jacek Anaszewski
2019-05-20 21:19 ` Dan Murphy
2019-05-21 17:40 ` Jacek Anaszewski
2019-05-21 18:25 ` Dan Murphy
2019-05-21 18:46 ` Jacek Anaszewski
2019-05-21 19:41 ` Dan Murphy
2019-05-21 20:40 ` Jacek Anaszewski
2019-05-14 19:11 ` Jacek Anaszewski [this message]
2019-05-22 19:27 [PATCH v4 0/6] LM36274 Introduction Dan Murphy
2019-05-22 19:37 ` Jacek Anaszewski
2019-05-22 19:39 ` Dan Murphy
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=aface058-d34c-9ae0-838d-7e8b0cfe6e10@gmail.com \
--to=jacek.anaszewski@gmail.com \
--cc=broonie@kernel.org \
--cc=dmurphy@ti.com \
--cc=lee.jones@linaro.org \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-leds@vger.kernel.org \
--cc=pavel@ucw.cz \
--cc=rdunlap@infradead.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).