linux-leds.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Martin Fuzzey <martin.fuzzey@flowbird.group>
To: Dan Murphy <dmurphy@ti.com>, jacek.anaszewski@gmail.com, pavel@ucw.cz
Cc: linux-leds@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v17 00/19] Multicolor Framework
Date: Fri, 15 Nov 2019 15:57:33 +0100	[thread overview]
Message-ID: <55c6a873-9ed7-0c00-b85b-7a0f7ae7046e@flowbird.group> (raw)
In-Reply-To: <20191114133023.32185-1-dmurphy@ti.com>

On 14/11/2019 14:30, Dan Murphy wrote:
> Hello
>
> Simple fix in the multicolor code where the extended registration call was not
> called in the devm_* function
>
> Thanks Martin F. for finding this issue.
>
> Hopefully this will be pulled in for the 5.5 merge window.

For patches 2, 3, 4

     Tested-by: Martin Fuzzey <martin.fuzzey@flowbird.group>

I have applied patch 1 to my tree too but, being just documentation, 
it's not testable.

I don't have a lp50xx but have written my own multicolor driver on top 
of this patchset (for a custom LED controller implemented in a MCU).


Martin



  parent reply	other threads:[~2019-11-15 14:57 UTC|newest]

Thread overview: 38+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-11-14 13:30 [PATCH v17 00/19] Multicolor Framework Dan Murphy
2019-11-14 13:30 ` [PATCH v17 01/19] dt: bindings: Add multicolor class dt bindings documention Dan Murphy
2019-11-14 13:30 ` [PATCH v17 02/19] dt-bindings: leds: Add multicolor ID to the color ID list Dan Murphy
2019-11-14 13:30 ` [PATCH v17 03/19] " Dan Murphy
2019-11-14 13:30 ` [PATCH v17 04/19] leds: multicolor: Introduce a multicolor class definition Dan Murphy
2019-11-14 13:30 ` [PATCH v17 05/19] dt: bindings: lp50xx: Introduce the lp50xx family of RGB drivers Dan Murphy
2019-11-14 13:30 ` [PATCH v17 06/19] leds: lp50xx: Add the LP50XX family of the RGB LED driver Dan Murphy
2019-11-14 13:30 ` [PATCH v17 07/19] dt: bindings: lp55xx: Be consistent in the document with LED acronym Dan Murphy
2019-12-22 18:25   ` Pavel Machek
2019-11-14 13:30 ` [PATCH v17 08/19] dt: bindings: lp55xx: Update binding for Multicolor Framework Dan Murphy
2019-11-14 13:30 ` [PATCH v17 09/19] ARM: dts: n900: Add reg property to the LP5523 channel node Dan Murphy
2019-12-22 18:27   ` Pavel Machek
2019-11-14 13:30 ` [PATCH v17 10/19] ARM: dts: imx6dl-yapp4: Add reg property to the lp5562 " Dan Murphy
2019-12-02  9:06   ` Shawn Guo
2019-12-02 13:03     ` Dan Murphy
2019-11-14 13:30 ` [PATCH v17 11/19] ARM: dts: ste-href: Add reg property to the LP5521 channel nodes Dan Murphy
2019-12-22 18:28   ` Pavel Machek
2019-11-14 13:30 ` [PATCH v17 12/19] leds: lp55xx: Convert LED class registration to devm_* Dan Murphy
2019-12-22 18:30   ` Pavel Machek
2020-01-03 15:44     ` Dan Murphy
2019-11-14 13:30 ` [PATCH v17 13/19] leds: lp55xx: Add multicolor framework support to lp55xx Dan Murphy
2019-11-14 13:30 ` [PATCH v17 14/19] leds: lp5523: Update the lp5523 code to add multicolor brightness function Dan Murphy
2019-11-14 13:30 ` [PATCH v17 15/19] leds: lp5521: Add multicolor framework multicolor brightness support Dan Murphy
2019-11-14 13:30 ` [PATCH v17 16/19] leds: lp55xx: Fix checkpatch file permissions issues Dan Murphy
2019-12-22 18:32   ` Pavel Machek
2019-11-14 13:30 ` [PATCH v17 17/19] leds: lp5523: Fix checkpatch issues in the code Dan Murphy
2019-12-22 18:33   ` Pavel Machek
2019-11-14 13:30 ` [PATCH v17 18/19] dt: bindings: Update lp55xx binding to recommended LED naming Dan Murphy
2019-12-22 18:33   ` Pavel Machek
2019-11-14 13:30 ` [PATCH v17 19/19] leds: lp55xx-common: Remove extern from lp55xx-common header Dan Murphy
2019-12-22 18:35   ` Pavel Machek
2020-01-03 15:43     ` Dan Murphy
2019-11-15 14:57 ` Martin Fuzzey [this message]
2019-12-09 13:22 ` [PATCH v17 00/19] Multicolor Framework Dan Murphy
2019-12-18 14:45 ` Dan Murphy
2020-01-08 13:48   ` Dan Murphy
2020-01-08 19:09     ` Jacek Anaszewski
2020-01-08 19:12       ` 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=55c6a873-9ed7-0c00-b85b-7a0f7ae7046e@flowbird.group \
    --to=martin.fuzzey@flowbird.group \
    --cc=dmurphy@ti.com \
    --cc=jacek.anaszewski@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).