linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jacek Anaszewski <jacek.anaszewski@gmail.com>
To: Lee Jones <lee.jones@linaro.org>
Cc: Dan Murphy <dmurphy@ti.com>,
	pavel@ucw.cz, linux-leds@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3 0/7] LMU Common code intro
Date: Wed, 1 May 2019 11:45:41 +0200	[thread overview]
Message-ID: <8166c0c1-facf-14da-7c71-5bc5a3cc23f7@gmail.com> (raw)
In-Reply-To: <34088323-9b40-7dea-5449-6a01bb721c00@gmail.com>

Ekhm, I forgot to add the main recipient.

Adding Lee.

On 5/1/19 12:05 AM, Jacek Anaszewski wrote:
> Hi Lee,
> 
> This patch set has dependency on the previous one for lm3532, which
> also touches ti-lmu.txt bindings, and for which I already created
> immutable branch. Now if I created another immutable branch for
> this patch set we would have to resolve conflicts between the two,
> as they would both be based on 5.1-rc1. Adds much overhead and
> is error prone. Therefore I propose to apply this patch set on
> top of my merge of LED tree with the immutable branch for lm3532.
> 
> Please let me know if you see it differently. I'll wait for your
> response until Friday, and then proceed with the above as I think
> it should be harmless for MFD.
> 
> Best regards,
> Jacek Anaszewski
> 
> On 4/30/19 9:17 PM, Dan Murphy wrote:
>> Hello
>>
>> I have added the Reviewed-by for dt bindings as well as made the 
>> Kconfig change
>> pointed out for the common code flag
>>
>> Dan
>>
>> Dan Murphy (7):
>>    dt-bindings: mfd: LMU: Fix lm3632 dt binding example
>>    dt-bindings: mfd: LMU: Add the ramp up/down property
>>    dt-bindings: mfd: LMU: Add ti,brightness-resolution
>>    leds: TI LMU: Add common code for TI LMU devices
>>    dt-bindings: ti-lmu: Modify dt bindings for the LM3697
>>    mfd: ti-lmu: Remove support for LM3697
>>    leds: lm3697: Introduce the lm3697 driver
>>
>>   .../devicetree/bindings/leds/leds-lm3697.txt  |  73 ++++
>>   .../devicetree/bindings/mfd/ti-lmu.txt        |  56 ++-
>>   drivers/leds/Kconfig                          |  15 +
>>   drivers/leds/Makefile                         |   2 +
>>   drivers/leds/leds-lm3697.c                    | 395 ++++++++++++++++++
>>   drivers/leds/ti-lmu-led-common.c              | 155 +++++++
>>   drivers/mfd/Kconfig                           |   2 +-
>>   drivers/mfd/ti-lmu.c                          |  17 -
>>   include/linux/mfd/ti-lmu-register.h           |  44 --
>>   include/linux/mfd/ti-lmu.h                    |   1 -
>>   include/linux/ti-lmu-led-common.h             |  47 +++
>>   11 files changed, 712 insertions(+), 95 deletions(-)
>>   create mode 100644 
>> Documentation/devicetree/bindings/leds/leds-lm3697.txt
>>   create mode 100644 drivers/leds/leds-lm3697.c
>>   create mode 100644 drivers/leds/ti-lmu-led-common.c
>>   create mode 100644 include/linux/ti-lmu-led-common.h
>>
> 
> 

-- 
Best regards,
Jacek Anaszewski

  reply	other threads:[~2019-05-01  9:45 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-04-30 19:17 [PATCH v3 0/7] LMU Common code intro Dan Murphy
2019-04-30 19:17 ` [PATCH v3 1/7] dt-bindings: mfd: LMU: Fix lm3632 dt binding example Dan Murphy
2019-04-30 19:17 ` [PATCH v3 2/7] dt-bindings: mfd: LMU: Add the ramp up/down property Dan Murphy
2019-04-30 22:01   ` Pavel Machek
2019-05-06 17:53     ` Dan Murphy
2019-04-30 19:17 ` [PATCH v3 3/7] dt-bindings: mfd: LMU: Add ti,brightness-resolution Dan Murphy
2019-04-30 19:17 ` [PATCH v3 4/7] leds: TI LMU: Add common code for TI LMU devices Dan Murphy
2019-04-30 19:23   ` Randy Dunlap
2019-04-30 19:30     ` Dan Murphy
2019-04-30 19:32       ` Jacek Anaszewski
2019-04-30 19:34         ` Dan Murphy
2019-04-30 19:17 ` [PATCH v3 5/7] dt-bindings: ti-lmu: Modify dt bindings for the LM3697 Dan Murphy
2019-04-30 22:05   ` Pavel Machek
2019-04-30 22:07     ` Dan Murphy
2019-04-30 22:08       ` Pavel Machek
2019-04-30 19:17 ` [PATCH v3 6/7] mfd: ti-lmu: Remove support for LM3697 Dan Murphy
2019-04-30 19:17 ` [PATCH v3 7/7] leds: lm3697: Introduce the lm3697 driver Dan Murphy
2019-04-30 22:05 ` [PATCH v3 0/7] LMU Common code intro Jacek Anaszewski
2019-05-01  9:45   ` Jacek Anaszewski [this message]
2019-05-08  6:21     ` 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=8166c0c1-facf-14da-7c71-5bc5a3cc23f7@gmail.com \
    --to=jacek.anaszewski@gmail.com \
    --cc=dmurphy@ti.com \
    --cc=lee.jones@linaro.org \
    --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).