[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <a9fb188c-8e88-8e80-2795-7f7504c35fcd@linaro.org>
Date: Sat, 5 Aug 2023 23:10:42 +0200
From: Krzysztof Kozlowski <krzysztof.kozlowski@...aro.org>
To: Conor Dooley <conor@...nel.org>, Fabio Estevam <festevam@...x.de>
Cc: robh+dt@...nel.org, krzysztof.kozlowski+dt@...aro.org,
conor+dt@...nel.org, devicetree@...r.kernel.org,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH v2 2/2] dt-bindings: media: Add OV5642
On 02/08/2023 17:25, Conor Dooley wrote:
> Hey,
>
> On Tue, Aug 01, 2023 at 08:40:47PM -0300, Fabio Estevam wrote:
>> Add DT bindings for OmniVision OV5642 Image Sensor.
>>
>> Signed-off-by: Fabio Estevam <festevam@...x.de>
>
> Thanks for doing this. It looks good to me, although I got a complaint
> from git while applying it locally:
> Applying: dt-bindings: trivial-devices: Remove the OV5642 entry
> Applying: dt-bindings: media: Add OV5642
> /stuff/linux/.git/worktrees/linux-dt/rebase-apply/patch:119: trailing whitespace.
>
> warning: 1 line adds whitespace errors.
>
> I think you can probably squash both patches and add a
Yes, they should be squashed, otherwise it is not really bisectable.
Compatible disappears after first patch... and the first patch does not
have any sense on its own. Even if this is not trivial device, removing
it without documentation is not the way.
Best regards,
Krzysztof
Powered by blists - more mailing lists