From: Michael Walle <michael@walle.cc>
To: Simon Glass <sjg@chromium.org>
Cc: U-Boot Mailing List <u-boot@lists.denx.de>,
Tom Rini <trini@konsulko.com>, Simon Glass <sjg@chromium.org>
Subject: Re: [PATCH 5/6] kontron_sl28: Use u-boot-update.bin instead of u-boot.update
Date: Thu, 24 Aug 2023 09:35:09 +0200 [thread overview]
Message-ID: <ef160d20e37f85f0bdcb145a11a7ae69@walle.cc> (raw)
In-Reply-To: <20230824030304.1555547-6-sjg@chromium.org>
Am 2023-08-24 05:02, schrieb Simon Glass:
> A '.update' extension is not allowed anymore, so change it.
>
> Signed-off-by: Simon Glass <sjg@chromium.org>
Looks good to me, as it is just an intermediate binary.
Acked-by: Michael Walle <michael@walle.cc>
next prev parent reply other threads:[~2023-08-24 7:35 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-24 3:02 [PATCH 0/6] Attempt to enforce standard extensions for build output Simon Glass
2023-08-24 3:02 ` [PATCH 1/6] binman: Require image filenames to have certain extensions Simon Glass
2023-08-24 3:02 ` [PATCH 2/6] buildman: Keep all permitted output files Simon Glass
2023-08-24 14:26 ` Tom Rini
2023-08-24 3:02 ` [PATCH 3/6] buildman: Show progress when regenerating the board.cfg file Simon Glass
2023-08-24 3:02 ` [PATCH 4/6] buildman: Start the clock when the build starts Simon Glass
2023-08-24 3:02 ` [PATCH 5/6] kontron_sl28: Use u-boot-update.bin instead of u-boot.update Simon Glass
2023-08-24 7:35 ` Michael Walle [this message]
2023-08-24 3:02 ` [PATCH 6/6] stm32mp15: Use u-boot-spl-stm32.bin instead of u-boot-spl.stm32 Simon Glass
2023-08-24 3:12 ` Marek Vasut
2023-08-24 14:25 ` Tom Rini
2023-08-24 15:09 ` Marek Vasut
2023-08-24 15:14 ` Tom Rini
2023-08-24 15:26 ` Marek Vasut
2023-08-29 16:28 ` Patrick DELAUNAY
2023-09-02 0:09 ` Simon Glass
2023-08-24 7:32 ` [PATCH 0/6] Attempt to enforce standard extensions for build output Michael Walle
2023-08-24 14:43 ` Simon Glass
2023-08-24 14:55 ` Michael Walle
2023-08-24 12:26 ` Neha Malcom Francis
2023-08-24 14:41 ` Simon Glass
2023-08-24 13:38 ` Tom Rini
2023-08-24 14:41 ` Simon Glass
2023-08-24 14:45 ` Tom Rini
2023-08-24 14:49 ` Simon Glass
2023-08-24 15:16 ` Tom Rini
2023-08-27 19:17 ` Alper Nebi Yasak
2023-08-28 17:54 ` Simon Glass
2023-08-28 18:53 ` Tom Rini
2023-08-31 10:20 ` Alper Nebi Yasak
2023-08-31 19:01 ` Simon Glass
2023-08-31 19:07 ` Tom Rini
2023-08-31 19:22 ` Simon Glass
2023-08-31 19:24 ` Tom Rini
2023-09-01 1:10 ` Simon Glass
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=ef160d20e37f85f0bdcb145a11a7ae69@walle.cc \
--to=michael@walle.cc \
--cc=sjg@chromium.org \
--cc=trini@konsulko.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