Re: (subset) [PATCH 1/2] dt-bindings: display: Use consistent indentation in the example

[Luca Ceresoli]

Hello Krzysztof, Laurent,

On Mon Sep 28, 2026 at 12:08 PM CEST, Laurent Pinchart wrote:
> On Mon, Sep 28, 2026 at 10:08:43AM +0200, Krzysztof Kozlowski wrote:
>> On 28/09/2026 08:58, Laurent Pinchart wrote:
>> > On Mon, Sep 28, 2026 at 08:03:18AM +0200, Krzysztof Kozlowski wrote:
>> >> On 28/09/2026 07:33, Luca Ceresoli wrote:
>> >>> On Sun, 13 Sep 2026 14:33:32 +0200, Krzysztof Kozlowski wrote:
>> >>>> Correct indentation in the examples to consistent 2- or 4-spaces
>> >>>> indentation to fix dt-check-style warnings ("example 0
>> >>>> [indent-consistent] indent mismatch ...").  Preferred is 4-spaces, but
>> >>>> re-indenting entire example just for that is too much churn.
>> >>>
>> >>> Applied, thanks!
>> >>>
>> >>> [1/2] dt-bindings: display: Use consistent indentation in the example
>> >>>       commit: 370c5d9004f8b754351981d59fc26851bf943e93
>> >>
>> >> Thanks, but I expected no one will pick it up, so I asked Rob to take
>> >> it, thus it is already queued.

Sorry that this caused confusion.

>> > Please explain your merge plans in the cover letter next time.
>>
>> The merge plan was this going through drm-misc. It got reviews, no one
>> applied, even Dmitry for msm only reviewed the msm-bits (second patch),
>> so I asked Rob to take it. This was not planned, but result of usual
>> drm-misc inactivity for bindings (many bindings were not taken in the
>> past or with noticeable delay/pings).

My personal rule of thumb to apply patches to drm-misc is to wait at least
(the latest of):

 * 2w after the patch has been sent
 * 1w after it's reviewed/acked

This is to give everyone reasonable time to chime in and nack if needed.

According to that policy, which is of course debatable and not ubiquitous,
this patch got applied timely.

> If that happens again, could you please reply to the series on the
> dri-devel list to tell it will be merged through the DT tree ? I don't
> think there's any issue with merging patches that way, it's just
> coordination that's lacking.

I agree a ping over e-mail or on #dri-devel would be good and less noisy.

But if the patch has multiple eligible branches an "applied, thanks" e-mail
would let everyone know. I do it very cheaply with 'b4 ty'.

Kind regards,
Luca

--
Luca Ceresoli, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com