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]
Date:   Mon, 18 Jul 2022 16:34:09 +0200
From:   Konrad Dybcio <konrad.dybcio@...ainline.org>
To:     Krzysztof Kozlowski <krzysztof.kozlowski@...aro.org>,
        ~postmarketos/upstreaming@...ts.sr.ht
Cc:     martin.botka@...ainline.org,
        angelogioacchino.delregno@...ainline.org,
        marijn.suijten@...ainline.org, jamipkettunen@...ainline.org,
        Andy Gross <agross@...nel.org>,
        Bjorn Andersson <bjorn.andersson@...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 2/6] dt-bindings: firmware: scm: Add compatible for SM6375



On 18.07.2022 16:29, Krzysztof Kozlowski wrote:
> On 16/07/2022 21:32, Konrad Dybcio wrote:
>> Add a SCM compatible for SM6375.
>>
>> Signed-off-by: Konrad Dybcio <konrad.dybcio@...ainline.org>
>> ---
>>  Documentation/devicetree/bindings/firmware/qcom,scm.txt | 1 +
>>  1 file changed, 1 insertion(+)
>>
>> diff --git a/Documentation/devicetree/bindings/firmware/qcom,scm.txt b/Documentation/devicetree/bindings/firmware/qcom,scm.txt
>> index b3f702cbed87..de7bb8b8d85e 100644
>> --- a/Documentation/devicetree/bindings/firmware/qcom,scm.txt
>> +++ b/Documentation/devicetree/bindings/firmware/qcom,scm.txt
>> @@ -35,6 +35,7 @@ Required properties:
>>   * "qcom,scm-sm8250"
>>   * "qcom,scm-sm8350"
>>   * "qcom,scm-sm8450"
>> + * "qcom,sm6375-scm"
> 
> Uh, I think we wanted to keep it consistent with existing ones, didn't we?
> 
I still haven't sent DT yet (need to get drivers in first), so I can do either,
though I thought it would be good practice to switch to the now-preferred
format and not have to add any more compatibles to the exception list.
> 
> Best regards,
> Krzysztof

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ