linux-kernel - running "make dtbs" for test builds

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

Message-ID: <8924490.SntxSU2FOC@wuerfel>
Date:	Mon, 18 Jul 2016 14:01:17 +0200
From:	Arnd Bergmann <arnd@...db.de>
To:	Fengguang Wu <lkp@...el.com>
Cc:	linux-kernel@...r.kernel.org, linux-arm-kernel@...ts.infradead.org,
	Fengguang Wu <fengguang.wu@...el.com>,
	Thierry Reding <thierry.reding@...il.com>,
	devicetree@...r.kernel.org,
	linux-kbuild <linux-kbuild@...r.kernel.org>
Subject: running "make dtbs" for test builds

Hi Fengguang,

I've recently run into a number of cases in which I pulled a branch that
was building fine with "make vmlinux", but that failed for "make dtbs",
and I wonder if this is something that could be checked by the kbuild
test robot so we catch it earlier.

There are parts of this:

- running "make" without a target will build the default image file
  and also do the "dtbs" target on ARM and other architectures. I
  don't know if this is what you do, or if you always build
  "make vmlinux ; make modules", which doesn't include it.
  The dtbs makefile target is available on arc, arm, arm64, h8300,
  metag, mips, nios2, and xtensa but not the others, so if you
  call it explicitly, that has to be in an architecture specific
  way.

- setting CONFIG_OF_ALL_DTBS will catch all files, not just the
  ones that are built by default for the set of configurations you
  have. It's possible to simply override this on the command line,
  using "make CONFIG_OF_ALL_DTBS=y", it doesn't actually have to
  be part of the configuration. The result is independent of the
  actual configuration, so it should be enough to do this once
  per architecture and source revision.

Is this something you can add?

	Arnd