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] [day] [month] [year] [list]
Date:   Sun, 16 Apr 2023 16:17:10 +0200
From:   Krzysztof Kozlowski <krzysztof.kozlowski@...aro.org>
To:     Jonathan Cameron <jic23@...nel.org>
Cc:     Lars-Peter Clausen <lars@...afoo.de>,
        Rob Herring <robh+dt@...nel.org>,
        Krzysztof Kozlowski <krzysztof.kozlowski+dt@...aro.org>,
        Andy Gross <agross@...nel.org>,
        Bjorn Andersson <andersson@...nel.org>,
        Siddartha Mohanadoss <smohanad@...eaurora.org>,
        linux-iio@...r.kernel.org, devicetree@...r.kernel.org,
        linux-kernel@...r.kernel.org
Subject: Re: [PATCH] dt-bindings: iio: adc: qcom,spmi-vadc: add 16 ratio of
 pre-scaling

On 16/04/2023 15:10, Jonathan Cameron wrote:
> On Sun, 16 Apr 2023 14:31:42 +0200
> Krzysztof Kozlowski <krzysztof.kozlowski@...aro.org> wrote:
> 
>> Document value of 16 for pre-scaling, already used in DTS and supported
>> by the Linux driver since long time:
>>
>>   sm7225-fairphone-fp4.dtb: adc@...0: channel@8:qcom,pre-scaling: 'oneOf' conditional failed, one must be fixed:
>>     10 was expected
>>     16 is not one of [1, 3, 4, 6, 20, 8, 10]
>>     81 was expected
>>
>> Fixes: e13d757279bb ("iio: adc: Add QCOM SPMI PMIC5 ADC driver")
>> Signed-off-by: Krzysztof Kozlowski <krzysztof.kozlowski@...aro.org>
> 
> I'm carrying an identical patch (though without the reordering) from Luca Weiss.
> I thought as the whole series was very late in the cycle that it was unlikely
> to be necessary to rush this in.
> 
> https://lore.kernel.org/all/20230414-pmi632-v1-5-fe94dc414832@z3ntu.xyz/
> 
> I see that patch is for the fairphone-fp3 adn this report is the fairphone-fp4.
> Is that the reason this is a fix?

Oh, I missed it. It's just something new and not yet in next maybe, so
thus I missed the fix.

Ignore this patch then, please.

Best regards,
Krzysztof

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ