From: Peter Korsgaard <peter@korsgaard.com>
To: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
Cc: Thomas Petazzoni <thomas.petazzoni@bootlin.com>,
Wojciech Nizinski <wojciech.nizinski@grinn-global.com>
Subject: Re: [Buildroot] [PATCH 1/1] board/freescale/common/imx: imx8-bootloader-prepare: enable error checking
Date: Thu, 02 May 2024 09:50:26 +0200 [thread overview]
Message-ID: <87bk5o8xfh.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <20240403230810.5e8b9e21@windsurf> (Thomas Petazzoni via buildroot's message of "Wed, 3 Apr 2024 23:08:10 +0200")
>>>>> "Thomas" == Thomas Petazzoni via buildroot <buildroot@buildroot.org> writes:
> On Thu, 14 Sep 2023 18:50:46 +0200
> Wojciech Nizinski <wojciech.nizinski@grinn-global.com> wrote:
>> Run script with 'errexit' bash option to detect any errors from
>> subcommands.
>>
>> It will fix situation where 'ddr_fw.bin' was missing but successfull
>> build created broken boot image. Post image script report this by:
>>
>> cat: /home/user/buildroot/output/images/ddr_fw.bin: No such file or
>> directory
>>
>> and build finish with success.
>>
>> Signed-off-by: Wojciech Nizinski <wojciech.nizinski@grinn-global.com>
>> ---
>> board/freescale/common/imx/imx8-bootloader-prepare.sh | 1 +
>> 1 file changed, 1 insertion(+)
> Applied to master after changing to use set -e. Thanks!
Committed to 2024.02.x, thanks.
--
Bye, Peter Korsgaard
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
prev parent reply other threads:[~2024-05-02 7:50 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-14 16:50 [Buildroot] [PATCH 1/1] board/freescale/common/imx: imx8-bootloader-prepare: enable error checking Wojciech Nizinski
2024-02-05 16:53 ` Sébastien Szymanski
2024-04-03 21:08 ` Thomas Petazzoni via buildroot
2024-05-02 7:50 ` Peter Korsgaard [this message]
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=87bk5o8xfh.fsf@dell.be.48ers.dk \
--to=peter@korsgaard.com \
--cc=buildroot@buildroot.org \
--cc=thomas.petazzoni@bootlin.com \
--cc=wojciech.nizinski@grinn-global.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.