From: Arnd Bergmann <arnd@arndb.de>
To: Fengguang Wu <lkp@intel.com>
Cc: linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
Fengguang Wu <fengguang.wu@intel.com>,
Thierry Reding <thierry.reding@gmail.com>,
devicetree@vger.kernel.org,
linux-kbuild <linux-kbuild@vger.kernel.org>
Subject: running "make dtbs" for test builds
Date: Mon, 18 Jul 2016 14:01:17 +0200 [thread overview]
Message-ID: <8924490.SntxSU2FOC@wuerfel> (raw)
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
next reply other threads:[~2016-07-18 12:01 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-18 12:01 Arnd Bergmann [this message]
2016-07-18 12:29 ` running "make dtbs" for test builds Fengguang Wu
[not found] ` <20160718122947.GA29820-q6ZYBFIlbFFi0tQiZxhdj1DQ4js95KgL@public.gmane.org>
2016-07-18 12:49 ` Arnd Bergmann
2016-07-18 12:41 ` Fengguang Wu
[not found] ` <20160718124122.GA30497-q6ZYBFIlbFFi0tQiZxhdj1DQ4js95KgL@public.gmane.org>
2016-07-18 12:52 ` Arnd Bergmann
2016-07-18 13:00 ` Fengguang Wu
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=8924490.SntxSU2FOC@wuerfel \
--to=arnd@arndb.de \
--cc=devicetree@vger.kernel.org \
--cc=fengguang.wu@intel.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@intel.com \
--cc=thierry.reding@gmail.com \
/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;
as well as URLs for NNTP newsgroup(s).