From: lkp@intel.com (Fengguang Wu)
To: linux-arm-kernel@lists.infradead.org
Subject: running "make dtbs" for test builds
Date: Mon, 18 Jul 2016 20:41:22 +0800 [thread overview]
Message-ID: <20160718124122.GA30497@wfg-t540p.sh.intel.com> (raw)
In-Reply-To: <8924490.SntxSU2FOC@wuerfel>
Hi Arnd,
On Mon, Jul 18, 2016 at 02:01:17PM +0200, Arnd Bergmann wrote:
>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.
We initially run "make" without vmlinux, however during bisect more
specific make targets will be used to speed it up. To do that it's
necessary to know the regex patterns of "make dtbs" error messages,
so that they can be correctly bisected.
Can you give some "make dtbs" error messages or patterns?
Thanks,
Fengguang
next prev parent reply other threads:[~2016-07-18 12:41 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-18 12:01 running "make dtbs" for test builds Arnd Bergmann
2016-07-18 12:29 ` Fengguang Wu
2016-07-18 12:49 ` Arnd Bergmann
2016-07-18 12:41 ` Fengguang Wu [this message]
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=20160718124122.GA30497@wfg-t540p.sh.intel.com \
--to=lkp@intel.com \
--cc=linux-arm-kernel@lists.infradead.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