linux-kernel - Re: Covering DT build in -next merge

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>] [day] [month] [year] [list]

Date:   Tue, 17 Oct 2023 13:20:26 -0700 (PDT)
From:   Palmer Dabbelt <palmer@...belt.com>
To:     broonie@...nel.org, Conor Dooley <conor@...nel.org>
CC:     Stephen Rothwell <sfr@...b.auug.org.au>,
        linux-next@...r.kernel.org, linux-kernel@...r.kernel.org,
        soc@...nel.org
Subject:     Re: Covering DT build in -next merge

On Tue, 17 Oct 2023 13:16:21 PDT (-0700), broonie@...nel.org wrote:
> Hi Stephen,
>
> I was wondering if it might be possible to add DTB builds for relevant
> architecutres to the -next merge checks (everything except x86 AFAIK)?
> Some current experience suggested to me that it might be helpful for
> bisecting problems found in testing, breakage building the DTBs causes
> hassle since where they're used in tree DTs are required to boot the
> kernel.
>
> At least for arm and arm64 the DT build is quick enough to be negligable
> in the context of building the kernel itself so hopefully it shouldn't
> add too much load to do this - it's just adding a 'make dtbs' (with
> appropriate cross build options) to the kernel build.

Pretty sure we're in the same shape for RISC-V these days.  +Conor, who 
would know for sure (as he made it work).

>
> Thanks,
> Mark