mail archive of the barebox mailing list
 help / color / mirror / Atom feed
From: Sascha Hauer <s.hauer@pengutronix.de>
To: Barebox List <barebox@lists.infradead.org>
Subject: [PATCH 03/10] MAKEALL: order configs alphabetically
Date: Tue,  2 May 2023 09:39:18 +0200	[thread overview]
Message-ID: <20230502073925.266116-4-s.hauer@pengutronix.de> (raw)
In-Reply-To: <20230502073925.266116-1-s.hauer@pengutronix.de>

Expanding wildcards returns the files in filesystem order. Sort them
alphabetically to compile the defconfigs in alphabetical order.

Signed-off-by: Sascha Hauer <s.hauer@pengutronix.de>
---
 MAKEALL | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/MAKEALL b/MAKEALL
index dd61f89827..5b1fb3ddd6 100755
--- a/MAKEALL
+++ b/MAKEALL
@@ -167,7 +167,7 @@ do_build() {
 	local arch=$1
 	local regex=$2
 
-	find arch/${arch}/configs -name "${regex}_defconfig" | while read i
+	find arch/${arch}/configs -name "${regex}_defconfig" | sort | while read i
 	do
 		local target=$(basename $i)
 
-- 
2.39.2




  parent reply	other threads:[~2023-05-02  7:41 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-02  7:39 [PATCH 00/10] MAKEALL updates Sascha Hauer
2023-05-02  7:39 ` [PATCH 01/10] MAKEALL: Configure before setting up CROSS_COMPILE Sascha Hauer
2023-05-02  7:39 ` [PATCH 02/10] MAKEALL: Select arm64 toolchain for 64bit ARM configs Sascha Hauer
2023-05-02  7:39 ` Sascha Hauer [this message]
2023-05-02  7:39 ` [PATCH 04/10] MAKEALL: Do not print sizes Sascha Hauer
2023-05-02  7:39 ` [PATCH 05/10] MAKEALL: Do not trap Sascha Hauer
2023-05-02  7:39 ` [PATCH 06/10] MAKEALL: fix printing number of compiled configs Sascha Hauer
2023-05-02  7:39 ` [PATCH 07/10] MAKEALL: support Kconfig fragments Sascha Hauer
2023-05-02  7:39 ` [PATCH 08/10] MAKEALL: rename variables Sascha Hauer
2023-05-02  7:39 ` [PATCH 09/10] MAKEALL: separate errors and warnings Sascha Hauer
2023-05-02  7:39 ` [PATCH 10/10] MAKEALL: allow multiple defconfigs as arguments Sascha Hauer

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=20230502073925.266116-4-s.hauer@pengutronix.de \
    --to=s.hauer@pengutronix.de \
    --cc=barebox@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