From: Lee Jones <lee.jones@linaro.org>
To: Jacek Anaszewski <jacek.anaszewski@gmail.com>
Cc: linux-leds@vger.kernel.org, linux-kernel@vger.kernel.org,
lgirdwood@gmail.com, broonie@kernel.org
Subject: Re: [GIT PULL] Immutable branch between LEDs, MFD and REGULATOR
Date: Wed, 22 May 2019 06:42:56 +0100 [thread overview]
Message-ID: <20190522054256.GA4574@dell> (raw)
In-Reply-To: <20190521203038.31946-1-jacek.anaszewski@gmail.com>
On Tue, 21 May 2019, Jacek Anaszewski wrote:
> The following changes since commit a188339ca5a396acc588e5851ed7e19f66b0ebd9:
>
> Linux 5.2-rc1 (2019-05-19 15:47:09 -0700)
>
> are available in the git repository at:
>
> git://git.kernel.org/pub/scm/linux/kernel/git/j.anaszewski/linux-leds.git tags/ti-lmu-led-drivers
>
> for you to fetch changes up to 13f5750a60b923d8f3f0e23902f2ece46dd733d7:
>
> leds: lm36274: Introduce the TI LM36274 LED driver (2019-05-21 20:34:19 +0200)
>
> ----------------------------------------------------------------
> TI LMU LED support rework and introduction of two new drivers
> with DT bindings:
>
> - leds-lm3697 (entails additions to lm363x-regulator.c)
> - leds-lm36274
> ----------------------------------------------------------------
> Dan Murphy (12):
> dt-bindings: mfd: LMU: Add the ramp up/down property
> dt-bindings: mfd: LMU: Add ti,brightness-resolution
> mfd: ti-lmu: Remove support for LM3697
> mfd: ti-lmu: Add LM36274 support to the ti-lmu
These patches were Acked "for my own reference", which means I'd
at least expect a discussion on how/where they would be applied.
It's fine for them to go in via the LED tree in this instance and I do
thank you for sending a PR. Next time can we at least agree on the
route-in though please?
> leds: TI LMU: Add common code for TI LMU devices
> dt-bindings: ti-lmu: Modify dt bindings for the LM3697
> leds: lm3697: Introduce the lm3697 driver
> regulator: lm363x: Make the gpio register enable flexible
> dt-bindings: mfd: Add lm36274 bindings to 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/leds/leds-lm3697.txt | 73 ++++
> Documentation/devicetree/bindings/mfd/ti-lmu.txt | 88 +++--
> drivers/leds/Kconfig | 23 ++
> drivers/leds/Makefile | 3 +
> drivers/leds/leds-lm36274.c | 174 +++++++++
> drivers/leds/leds-lm3697.c | 395 +++++++++++++++++++++
> drivers/leds/leds-ti-lmu-common.c | 156 ++++++++
> drivers/mfd/Kconfig | 5 +-
> drivers/mfd/ti-lmu.c | 23 +-
> drivers/regulator/Kconfig | 2 +-
> drivers/regulator/lm363x-regulator.c | 56 ++-
> include/linux/leds-ti-lmu-common.h | 47 +++
> include/linux/mfd/ti-lmu-register.h | 63 ++--
> include/linux/mfd/ti-lmu.h | 5 +-
> 15 files changed, 1112 insertions(+), 83 deletions(-)
> create mode 100644 Documentation/devicetree/bindings/leds/leds-lm36274.txt
> create mode 100644 Documentation/devicetree/bindings/leds/leds-lm3697.txt
> create mode 100644 drivers/leds/leds-lm36274.c
> create mode 100644 drivers/leds/leds-lm3697.c
> create mode 100644 drivers/leds/leds-ti-lmu-common.c
> create mode 100644 include/linux/leds-ti-lmu-common.h
--
Lee Jones [李琼斯]
Linaro Services Technical Lead
Linaro.org │ Open source software for ARM SoCs
Follow Linaro: Facebook | Twitter | Blog
next prev parent reply other threads:[~2019-05-22 5:42 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-21 20:30 [GIT PULL] Immutable branch between LEDs, MFD and REGULATOR Jacek Anaszewski
2019-05-21 21:15 ` Mark Brown
2019-05-22 0:48 ` Dan Murphy
2019-05-22 0:48 ` Dan Murphy
2019-05-22 10:59 ` Mark Brown
2019-05-22 18:27 ` Jacek Anaszewski
2019-05-22 19:02 ` Mark Brown
2019-05-29 20:44 ` Jacek Anaszewski
2019-05-22 5:42 ` Lee Jones [this message]
2019-05-22 19:01 ` Jacek Anaszewski
2019-05-23 8:31 ` Lee Jones
2019-05-23 20:07 ` Jacek Anaszewski
2019-05-24 11:56 ` Mark Brown
2019-05-29 20:44 ` Jacek Anaszewski
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=20190522054256.GA4574@dell \
--to=lee.jones@linaro.org \
--cc=broonie@kernel.org \
--cc=jacek.anaszewski@gmail.com \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-leds@vger.kernel.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 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.