[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20240220082026.GG10170@google.com>
Date: Tue, 20 Feb 2024 08:20:26 +0000
From: Lee Jones <lee@...nel.org>
To: Dharma.B@...rochip.com
Cc: krzysztof.kozlowski@...aro.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, 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 Tue, 20 Feb 2024, 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
> series, but unfortunately, I neglected to explicitly mention these
> dependencies. I understand the importance of clear communication in our
> collaborative efforts. Please feel free to provide guidance on how I can
> assist you further in resolving this matter.
If this continues to be an issue, I can just remove the commit.
--
Lee Jones [李琼斯]
Powered by blists - more mailing lists