[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <370bde1d-75f1-4ae2-a720-07fac8afaf5d@oss.qualcomm.com>
Date: Mon, 8 Dec 2025 03:59:50 +0100
From: Krzysztof Kozlowski <krzysztof.kozlowski@....qualcomm.com>
To: Rodrigo Gobbi <rodrigo.gobbi.7@...il.com>
Cc: gregkh@...uxfoundation.org, robh@...nel.org, krzk+dt@...nel.org,
conor+dt@...nel.org, davidm@...uge.net, ~lkcamp/patches@...ts.sr.ht,
linux-usb@...r.kernel.org, devicetree@...r.kernel.org,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH v2] dt-bindings: usb: maxim,max3421: convert to DT schema
On 06/12/2025 14:38, Rodrigo Gobbi wrote:
> On 11/7/25 05:03, Krzysztof Kozlowski wrote:
>>
>> You commit msg explain any unusual changes - like modifying binding
>> while ONLY converting it - and WHY you are doing the unusual changes.
>>
>> Best regards,
>> Krzysztof
>>
>
> Hi, Krzysztof,
> I was wondering about this again and I need to clarify the expectations here.
> So my v2 patch is only doing the conversion from txt to yaml without any additional
> changes. That being said, at v2, there are no new properties and no unusual changes.
>
> What happened was that under the ---, in order to save the lore and the previous discussion
> from v1, I`ve quoted the sentence about the "maxim,vbus-en-pin" prop from v1. Here, at v2,
> what I meant under the --- was that the "maxim,vbus-en-pin" was not new and it already existed
> in .txt file and the driver is already expecting that.
>
> So, even if I send a v3, it will be exactly the same direct conversion with the same commit msg
> because nothing was changed from txt.
> Maybe my intention was not right, my idea was to just save the lore/"answer" a previous point
> raised inside ---.
>
> Tks and best regards.
Indeed, I think I misread or went too fast through your changelog.
Everything looks correct, thanks for clarification.
Best regards,
Krzysztof
Powered by blists - more mailing lists