linux-kernel - Re: [PATCH v3 0/2] memory: omap-gpmc: Allow module build

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: <897a05fd-a568-9d33-dc20-5de4e5d2188f@linaro.org>
Date:   Wed, 13 Apr 2022 15:00:55 +0200
From:   Krzysztof Kozlowski <krzysztof.kozlowski@...aro.org>
To:     Roger Quadros <rogerq@...nel.org>
Cc:     linux-omap@...r.kernel.org, nm@...com,
        linux-kernel@...r.kernel.org, kishon@...com, tony@...mide.com,
        miquel.raynal@...tlin.com, vigneshr@...com
Subject: Re: [PATCH v3 0/2] memory: omap-gpmc: Allow module build

On 13/04/2022 14:56, Roger Quadros wrote:
>>
>> If you have spare time, maybe you could investigate the compile testing
>> on other platforms as well and if something fails, fix it. But it seems
>> it is separate problem.
>>
> 
> I won't be able to test on all platforms. I'm ok to not add more dependency and
> just drop COMPILE_TEST.

I understand that. You can still test 8-12 popular ones on a regular
Ubuntu machine (there are like 10 or 12 cross compile toolchains now in
standard Ubuntu repos).

Another way is to put your patches on Github and ask kbuild folks to
test your trees. I think this was the repo (but double check):
https://github.com/fengguang/lkp-tests


Best regards,
Krzysztof