From: Jacek Anaszewski <jacek.anaszewski@gmail.com>
To: Pavel Machek <pavel@ucw.cz>, Dan Murphy <dmurphy@ti.com>
Cc: robh+dt@kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org, lee.jones@linaro.org,
linux-omap@vger.kernel.org, linux-leds@vger.kernel.org
Subject: Re: [RFC PATCH v2 2/9] dt-bindings: ti-lmu: Remove LM3697
Date: Wed, 3 Oct 2018 22:46:40 +0200 [thread overview]
Message-ID: <f4ed1450-6c99-e4c6-0092-f355ab3278f7@gmail.com> (raw)
In-Reply-To: <20181003130154.GA20418@amd>
On 10/03/2018 03:01 PM, Pavel Machek wrote:
> On Wed 2018-10-03 07:24:23, Dan Murphy wrote:
>> Hello
>>
>> On 10/02/2018 02:28 AM, Pavel Machek wrote:
>>> On Fri 2018-09-28 13:29:47, Dan Murphy wrote:
>>>> Remove support for the LM3697 LED device
>>>> from the ti-lmu. The LM3697 will be supported
>>>> via a stand alone LED driver.
>>>>
>>>> Signed-off-by: Dan Murphy <dmurphy@ti.com>
>>>
>>> NAK, for reasons I explained before. Please add it to the patch so
>>> that it does not get applied by mistake. Ouch and AFAICT Rob was not
>>> happy with this either.
>>>
>>> Yes, you are creating new drivers, ok; but that does _not_ mean you
>>> should create new binding.
>>
>> I am copying my comment here on the review of this original binding for
>> records
>>
>> I found the review or at least the reference for the ti-lmu.txt binding.
>>
>> https://lore.kernel.org/patchwork/patch/764180/
>>
>> Does not appear that the binding was sent to the device tree mail list.
>> (Maybe that email list did not exist in Feb 2017).
>
> Quick google shows:
>
> https://lwn.net/Articles/666023/
This link refreshed my memory and allowed me to recall Milo's patch set
from the end of 2015, and the related discussion. I had an impression
that I had had some request regarding the bindings but there was no
follow-up.
I've googled that thread [0] and it proved I was right [1].
>From Milo's messages we can infer that there will be next
version of the patch set and it appeared but over a year later [2],
and without the leds-lm3633 driver and related bindings, and without
drivers/video/backlight/ti-lmu-backlight-core.c.
Patch set gets merged despite dangling DT references.
Dan, I propose you to resend the patch removing the bindings from
MFD, and explain the rationale in the patch below commit message
after "---" .
> Now can we stop this nonsense? If there is a problem with the binding,
> submit patches to fix the problem.
[0]
https://lore.kernel.org/lkml/1448521025-2796-1-git-send-email-milo.kim@ti.com/
[1] https://lore.kernel.org/lkml/56656468.8020300@samsung.com/
[2]
https://www.mail-archive.com/linux-kernel@vger.kernel.org/msg1341860.html
--
Best regards,
Jacek Anaszewski
next prev parent reply other threads:[~2018-10-03 20:46 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-28 18:29 [RFC PATCH v2 0/9] TI LMU and Dedicated Drivers Dan Murphy
2018-09-28 18:29 ` [RFC PATCH v2 1/9] leds: add TI LMU backlight driver Dan Murphy
2018-10-02 7:56 ` Pavel Machek
2018-10-02 12:32 ` Dan Murphy
2018-10-02 18:52 ` Jacek Anaszewski
2018-10-02 22:07 ` Pavel Machek
2018-10-03 12:00 ` Dan Murphy
2018-10-03 12:10 ` Dan Murphy
2018-09-28 18:29 ` [RFC PATCH v2 2/9] dt-bindings: ti-lmu: Remove LM3697 Dan Murphy
2018-10-02 7:28 ` Pavel Machek
2018-10-03 12:24 ` Dan Murphy
2018-10-03 13:01 ` Pavel Machek
2018-10-03 20:46 ` Jacek Anaszewski [this message]
2018-10-04 13:26 ` Dan Murphy
2018-09-28 18:29 ` [RFC PATCH v2 3/9] mfd: ti-lmu: Remove support for LM3697 Dan Murphy
2018-09-28 18:29 ` [RFC PATCH v2 4/9] dt-bindings: leds: Add bindings for lm3697 driver Dan Murphy
2018-09-28 18:29 ` [RFC PATCH v2 5/9] leds: lm3697: Introduce the " Dan Murphy
2018-09-28 18:29 ` [RFC PATCH v2 6/9] dt-bindings: leds: Add support for the LM3633 Dan Murphy
2018-09-28 18:29 ` [RFC PATCH v2 7/9] leds: lm3633: Introduce the lm3633 driver Dan Murphy
2018-09-28 18:29 ` [RFC PATCH v2 8/9] dt-bindings: leds: Add the LM3632 LED dt binding Dan Murphy
2018-09-28 18:29 ` [RFC PATCH v2 9/9] leds: lm3632: Introduce the TI LM3632 driver 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=f4ed1450-6c99-e4c6-0092-f355ab3278f7@gmail.com \
--to=jacek.anaszewski@gmail.com \
--cc=devicetree@vger.kernel.org \
--cc=dmurphy@ti.com \
--cc=lee.jones@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-leds@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=pavel@ucw.cz \
--cc=robh+dt@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 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).