U-Boot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Masahiro Yamada <yamada.m@jp.panasonic.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH 1/2] MAKEALL: run genboardscfg.py all the time
Date: Fri, 22 Aug 2014 14:33:40 +0900	[thread overview]
Message-ID: <1408685621-12867-2-git-send-email-yamada.m@jp.panasonic.com> (raw)
In-Reply-To: <1408685621-12867-1-git-send-email-yamada.m@jp.panasonic.com>

This commit makes sure boards.cfg is up to date before starting
the build tests.  tools/genboardscfg.py exits immediately printing
"boards.cfg is up to date. Nothing to do." when boards.cfg is
already new.

Signed-off-by: Masahiro Yamada <yamada.m@jp.panasonic.com>
---

 MAKEALL | 11 ++++-------
 1 file changed, 4 insertions(+), 7 deletions(-)

diff --git a/MAKEALL b/MAKEALL
index 2e826c1..4822054 100755
--- a/MAKEALL
+++ b/MAKEALL
@@ -171,13 +171,10 @@ GNU_MAKE=$(scripts/show-gnu-make) || {
 # echo "Remaining arguments:"
 # for arg do echo '--> '"\`$arg'" ; done
 
-if [ ! -r boards.cfg ]; then
-	echo "Could not find boards.cfg"
-	tools/genboardscfg.py || {
-		echo "Failed to generate boards.cfg" >&2
-		exit 1
-	}
-fi
+tools/genboardscfg.py || {
+	echo "Failed to generate boards.cfg" >&2
+	exit 1
+}
 
 FILTER="\$1 !~ /^#/"
 [ "$opt_a" ] && FILTER="${FILTER} && $opt_a"
-- 
1.9.1

  reply	other threads:[~2014-08-22  5:33 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-08-22  5:33 [U-Boot] [PATCH 0/2] MAKEALL, buildman: run genboardscfg.py to make sure boards.cfg is new Masahiro Yamada
2014-08-22  5:33 ` Masahiro Yamada [this message]
2014-08-29 14:40   ` [U-Boot] [U-Boot, 1/2] MAKEALL: run genboardscfg.py all the time Tom Rini
2014-08-22  5:33 ` [U-Boot] [PATCH 2/2] buildman: " Masahiro Yamada
2014-08-23  1:49   ` Simon Glass
2014-08-29 14:40   ` [U-Boot] [U-Boot, " Tom Rini

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=1408685621-12867-2-git-send-email-yamada.m@jp.panasonic.com \
    --to=yamada.m@jp.panasonic.com \
    --cc=u-boot@lists.denx.de \
    /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