From: Dan Murphy <dmurphy@ti.com>
To: Lee Jones <lee.jones@linaro.org>
Cc: jacek.anaszewski@gmail.com, pavel@ucw.cz, broonie@kernel.org,
lgirdwood@gmail.com, linux-leds@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v6 0/5] LM36274 Introduction
Date: Mon, 24 Jun 2019 12:20:26 -0500 [thread overview]
Message-ID: <3d2aa88c-c21c-b3a9-c8d9-fdb3a8fc3858@ti.com> (raw)
In-Reply-To: <20190624144217.GJ4699@dell>
Lee
On 6/24/19 9:42 AM, Lee Jones wrote:
> On Wed, 05 Jun 2019, Dan Murphy wrote:
>
>> Hello
>>
>> The v5 patchset missed adding in the new validation code.
>> Patch 1 of the v5 series was squashed into patch 4 of the v5 series.
>> So this will reduce the patchset by 1.
>>
>> Sorry for the extra noise on the patchsets. The change was lost when I converted
>> the patches from the mainline branch to the LED branch.
>>
>> This change was made on top of the branch
>>
>> repo: https://git.kernel.org/pub/scm/linux/kernel/git/j.anaszewski/linux-leds.git
>> branch: ti-lmu-led-drivers
>>
>>
>> Dan Murphy (5):
>> 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 | 8 +
>> 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 | 78 +++++++-
>> include/linux/mfd/ti-lmu-register.h | 23 +++
>> include/linux/mfd/ti-lmu.h | 4 +
>> 11 files changed, 437 insertions(+), 8 deletions(-)
>> create mode 100644 Documentation/devicetree/bindings/leds/leds-lm36274.txt
>> create mode 100644 drivers/leds/leds-lm36274.c
> Can you finish of satisfying everyone's comments and re-send with all
> the Acks you've collected so far? If you turn this around quickly,
> you might still get into v5.3.
>
The changes were made by Jacek and I reviewed and tested them
https://lkml.org/lkml/2019/6/11/455
next prev parent reply other threads:[~2019-06-24 17:20 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-05 12:56 [PATCH v6 0/5] LM36274 Introduction Dan Murphy
2019-06-05 12:56 ` [PATCH v6 1/5] dt-bindings: mfd: Add lm36274 bindings to ti-lmu Dan Murphy
2019-06-05 12:56 ` [PATCH v6 2/5] mfd: ti-lmu: Add LM36274 support to the ti-lmu Dan Murphy
2019-06-06 9:52 ` Pavel Machek
2019-06-05 12:56 ` [PATCH v6 3/5] regulator: lm363x: Add support for LM36274 Dan Murphy
2019-06-05 18:17 ` Mark Brown
2019-06-06 9:53 ` Pavel Machek
2019-06-05 12:56 ` [PATCH v6 4/5] dt-bindings: leds: Add LED bindings for the LM36274 Dan Murphy
2019-06-06 10:01 ` Pavel Machek
2019-06-05 12:56 ` [PATCH v6 5/5] leds: lm36274: Introduce the TI LM36274 LED driver Dan Murphy
2019-06-06 10:07 ` Pavel Machek
2019-06-06 10:07 ` Pavel Machek
2019-06-06 11:25 ` Dan Murphy
2019-06-05 19:31 ` [PATCH v6 0/5] LM36274 Introduction Jacek Anaszewski
2019-06-11 12:17 ` Dan Murphy
2019-06-24 14:42 ` Lee Jones
2019-06-24 17:20 ` Dan Murphy [this message]
2019-06-25 6:30 ` 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=3d2aa88c-c21c-b3a9-c8d9-fdb3a8fc3858@ti.com \
--to=dmurphy@ti.com \
--cc=broonie@kernel.org \
--cc=jacek.anaszewski@gmail.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 \
/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).