All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jacek Anaszewski <jacek.anaszewski@gmail.com>
To: Dan Murphy <dmurphy@ti.com>,
	pavel@ucw.cz, broonie@kernel.org, lgirdwood@gmail.com
Cc: lee.jones@linaro.org, linux-leds@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH v6 0/5] LM36274 Introduction
Date: Wed, 5 Jun 2019 21:31:36 +0200	[thread overview]
Message-ID: <cb41fea8-4cc6-bf0d-8006-6441ba8f2213@gmail.com> (raw)
In-Reply-To: <20190605125634.7042-1-dmurphy@ti.com>

Hi Dan,

Thank you for the v6.

Patches 4/5 and 5/5 don't contain amendments I made to
the respective patches on the ib-leds-mfd-regulator branch
(that address issues raised by Pavel), so I just kept those
unchanged. Besides that I updated the remaining ones.

Please check the ib-leds-mfd-regulator branch. I'll create a pull
request once I get a confirmation from you saying that everything
is as expected.

Best regards,
Jacek Anaszewski

On 6/5/19 2:56 PM, 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
> 

  parent reply	other threads:[~2019-06-05 19:31 UTC|newest]

Thread overview: 27+ 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 ` 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   ` 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-05 12:56   ` 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 12:56   ` 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-05 12:56   ` 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-05 12:56   ` 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-06 11:25       ` Dan Murphy
2019-06-05 19:31 ` Jacek Anaszewski [this message]
2019-06-11 12:17   ` [PATCH v6 0/5] LM36274 Introduction Dan Murphy
2019-06-11 12:17     ` Dan Murphy
2019-06-24 14:42 ` Lee Jones
2019-06-24 17:20   ` Dan Murphy
2019-06-24 17:20     ` Dan Murphy
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=cb41fea8-4cc6-bf0d-8006-6441ba8f2213@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 \
    /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.