From: Mark Brown <broonie@kernel.org>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Linux Next Mailing List <linux-next@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
soc@kernel.org
Subject: Covering DT build in -next merge
Date: Tue, 17 Oct 2023 21:16:21 +0100 [thread overview]
Message-ID: <ZS7rlTZLr0m1OEv8@sirena.org.uk> (raw)
[-- Attachment #1: Type: text/plain, Size: 653 bytes --]
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.
Thanks,
Mark
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next reply other threads:[~2023-10-17 20:16 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-17 20:16 Mark Brown [this message]
2023-10-17 20:20 ` Covering DT build in -next merge Palmer Dabbelt
2023-10-17 21:53 ` Conor Dooley
2023-10-18 6:11 ` Stephen Rothwell
2023-10-18 12:12 ` Mark Brown
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=ZS7rlTZLr0m1OEv8@sirena.org.uk \
--to=broonie@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
--cc=soc@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox