linux-kernel - Re: [PATCH] arm64: dts: qcom: sc8280xp-pmics: fix pon compatible and registers

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <fac15b28-ef4a-dd7d-f0ac-51518d9dc1be@linaro.org>
Date:   Mon, 3 Apr 2023 15:47:28 +0200
From:   Krzysztof Kozlowski <krzysztof.kozlowski@...aro.org>
To:     Johan Hovold <johan@...nel.org>
Cc:     Johan Hovold <johan+linaro@...nel.org>,
        Bjorn Andersson <andersson@...nel.org>,
        Andy Gross <agross@...nel.org>,
        Konrad Dybcio <konrad.dybcio@...aro.org>,
        Rob Herring <robh+dt@...nel.org>,
        Krzysztof Kozlowski <krzysztof.kozlowski+dt@...aro.org>,
        linux-arm-msm@...r.kernel.org, devicetree@...r.kernel.org,
        linux-kernel@...r.kernel.org
Subject: Re: [PATCH] arm64: dts: qcom: sc8280xp-pmics: fix pon compatible and
 registers

On 03/04/2023 15:11, Johan Hovold wrote:
> On Mon, Apr 03, 2023 at 02:46:41PM +0200, Krzysztof Kozlowski wrote:
>> On 03/04/2023 14:33, Krzysztof Kozlowski wrote:
>>> On 03/04/2023 12:54, Johan Hovold wrote:
> 
>>>> The problem is that the driver was updated before the binding was so the
>>>> above mentioned probe error has been there since this file was merged.
>>>
>>> I grepped and that commit did not have such compatible. Are you saying
>>> that the kernel which was released with this commit already had that
>>> compatible in driver (through different merge/tree)?
>>
>> So I double checked, the commit ccd3517faf18 (which is being "fixed")
>> was introduced in v6.0-rc1. v6.0-rc1 did not have "qcom,pmk8350-pon"
>> compatible, thus it could not be fixed that way. Therefore this cannot
>> be logically fix for that commit from that release.
> 
> Now you're just making shit up. A fix is a fix for mainline, period. If

Since this is your second mail in such tone and such phrases, I am not
going to keep discussing this. Regardless of differences in opinion, you
should keep the tone appropriate.

Best regards,
Krzysztof