linux-kernel - Re: [PATCH 2/2] dmaengine: ti: Do not enable by default during compile testing

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]

Message-ID: <2f0e8807-d37c-4491-be6e-c04e3e9032e6@linaro.org>
Date: Sun, 6 Apr 2025 19:43:05 +0200
From: Krzysztof Kozlowski <krzysztof.kozlowski@...aro.org>
To: Péter Ujfalusi <peter.ujfalusi@...il.com>,
 Vinod Koul <vkoul@...nel.org>, dmaengine@...r.kernel.org,
 linux-kernel@...r.kernel.org
Subject: Re: [PATCH 2/2] dmaengine: ti: Do not enable by default during
 compile testing

On 06/04/2025 18:08, Péter Ujfalusi wrote:
> 
> 
> On 4/4/25 3:21 PM, Krzysztof Kozlowski wrote:
>> Enabling the compile test should not cause automatic enabling of all
>> drivers.
> 
> The scope of compile test has changed?

No, it's the same.

> These drivers will likely not going to be compile tested from now on in

Why? They are. That's why allyesconfig you have.

> practice on other that the platforms they are used?
> 
> It gave a piece of mind to know that the code compiles on ppc/x86/etc
> also or it is no longer important sanity check?

And nothing changes here. They will be compile tested on all these other
archs the same as all other arch/soc specific drivers, which do exactly
what I am doing here.

Best regards,
Krzysztof