linux-kernel - Re: [PATCH] arm/arm64: samsung: Enable W=1 on dtbs by default

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:   Fri, 17 Nov 2023 11:19:28 +0100
From:   Krzysztof Kozlowski <krzysztof.kozlowski@...aro.org>
To:     Rob Herring <robh@...nel.org>,
        Alim Akhtar <alim.akhtar@...sung.com>,
        Conor Dooley <conor+dt@...nel.org>
Cc:     linux-arm-kernel@...ts.infradead.org,
        linux-samsung-soc@...r.kernel.org, devicetree@...r.kernel.org,
        linux-kernel@...r.kernel.org
Subject: Re: [PATCH] arm/arm64: samsung: Enable W=1 on dtbs by default

On 16/11/2023 22:17, Rob Herring wrote:
> Samsung platforms are clean of W=1 dtc warnings, so enable the warnings
> by default. This way submitters don't have to remember to run a W=1
> build of the .dts files and the grumpiness of the maintainers can be
> reduced.
> 
> Signed-off-by: Rob Herring <robh@...nel.org>
> ---
> Well, there's a couple of warnings on 32-bit, but they look fixable to
> me.
> 
> There's a few other platforms we could do this to. Sadly, they are still
> the minority. Otherwise, we could change the default and add a flag to
> disable (I_STILL_HAVENT_FIXED_MY_PLATFORMS=1).

64-bit has still few warnings:
https://krzk.eu/#/builders/29/builds/3710/steps/26/logs/warnings__6_

I guess these could be fixed by changing ports to port in the DTS and
bindings. I assume drivers are ready for it.

32-bit I fixed in this cycle - last three commits - so all Samsung
32-bit platforms are free from W=1 dtc warnings (yay!).

Best regards,
Krzysztof