[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <e6fdfb54-aa2c-4c17-a5c2-4d12abf2591c@linaro.org>
Date: Tue, 20 Feb 2024 09:43:21 +0100
From: Krzysztof Kozlowski <krzysztof.kozlowski@...aro.org>
To: Dharma.B@...rochip.com, lee@...nel.org, sam@...nborg.org,
bbrezillon@...nel.org, maarten.lankhorst@...ux.intel.com,
mripard@...nel.org, tzimmermann@...e.de, airlied@...il.com, daniel@...ll.ch,
robh+dt@...nel.org, krzysztof.kozlowski+dt@...aro.org, conor+dt@...nel.org,
Nicolas.Ferre@...rochip.com, alexandre.belloni@...tlin.com,
claudiu.beznea@...on.dev, dri-devel@...ts.freedesktop.org,
devicetree@...r.kernel.org, linux-arm-kernel@...ts.infradead.org,
linux-kernel@...r.kernel.org, thierry.reding@...il.com,
u.kleine-koenig@...gutronix.de, linux-pwm@...r.kernel.org
Cc: Hari.PrasathGE@...rochip.com, Manikandan.M@...rochip.com,
Conor.Dooley@...rochip.com
Subject: Re: (subset) [linux][PATCH v6 3/3] dt-bindings: mfd: atmel,hlcdc:
Convert to DT schema format
On 20/02/2024 04:34, Dharma.B@...rochip.com wrote:
> Hi Krzysztof,
>
> On 12/02/24 3:53 pm, Krzysztof Kozlowski wrote:
>> EXTERNAL EMAIL: Do not click links or open attachments unless you know the content is safe
>>
>> On 08/02/2024 11:43, Lee Jones wrote:
>>> On Fri, 02 Feb 2024 05:47:33 +0530, Dharma Balasubiramani wrote:
>>>> Convert the atmel,hlcdc binding to DT schema format.
>>>>
>>>> Align clocks and clock-names properties to clearly indicate that the LCD
>>>> controller expects lvds_pll_clk when interfaced with the lvds display. This
>>>> alignment with the specific hardware requirements ensures accurate device tree
>>>> configuration for systems utilizing the HLCDC IP.
>>>>
>>>> [...]
>>>
>>> Applied, thanks!
>>>
>>> [3/3] dt-bindings: mfd: atmel,hlcdc: Convert to DT schema format
>>> commit: cb946db1335b599ece363d33966bf653ed0fa58a
>>>
>>
>> Next is still failing.
>>
>> Dharma,
>> You must explain and clearly mark dependencies between patches.
>
> I sincerely apologize for any confusion caused by the oversight. I have
> organized the patches according to their dependencies in the patch
Does it mean that all your other patchsets which contain multiple
patches have dependencies? That would be the meaning of above approach.
Unfortunately that's not good... I'll comment in other places for
individual issues.
Best regards,
Krzysztof
Powered by blists - more mailing lists