From: Tom Rini <trini@konsulko.com>
To: u-boot@lists.denx.de
Subject: [PATCH v3 2/4] spl: fit: fail fit loading in case of FDT appending error
Date: Wed, 8 Jul 2020 20:22:28 -0400 [thread overview]
Message-ID: <20200709002228.GY1306@bill-the-cat> (raw)
In-Reply-To: <20200527115621.1062-3-dariobin@libero.it>
On Wed, May 27, 2020 at 01:56:19PM +0200, Dario Binacchi wrote:
> If uboot does not embed its device tree and the FIT loading function
> returns error in case of failure in the FDT append, the redundant itb
> image could be loaded.
>
> cc: Michael Trimarchi <michael@amarulasolutions.com>
> Signed-off-by: Dario Binacchi <dariobin@libero.it>
> Reviewed-by: Michael Trimarchi <michael@amarulasolutions.com>
> Reviewed-by: Simon Glass <sjg@chromium.org>
Applied to u-boot/master, thanks!
--
Tom
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 659 bytes
Desc: not available
URL: <https://lists.denx.de/pipermail/u-boot/attachments/20200708/f4970c34/attachment.sig>
next prev parent reply other threads:[~2020-07-09 0:22 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-27 11:56 [PATCH v3 0/4] Fix the SPL loading of a FIT image from NAND Dario Binacchi
2020-05-27 11:56 ` [PATCH v3 1/4] spl: fix format of function documentation Dario Binacchi
2020-05-31 14:08 ` Simon Glass
2020-07-09 0:22 ` Tom Rini
2020-05-27 11:56 ` [PATCH v3 2/4] spl: fit: fail fit loading in case of FDT appending error Dario Binacchi
2020-05-31 14:08 ` Simon Glass
2020-07-09 0:22 ` Tom Rini [this message]
2020-05-27 11:56 ` [PATCH v3 3/4] spl: fit: nand: fix fit loading in case of bad blocks Dario Binacchi
2020-06-06 19:23 ` Michael Nazzareno Trimarchi
2020-07-09 0:22 ` Tom Rini
2020-05-27 11:56 ` [PATCH v3 4/4] spl: fit: improve spl_nand_fit_read(...) readability Dario Binacchi
2020-05-31 14:08 ` Simon Glass
2020-07-09 0:22 ` 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=20200709002228.GY1306@bill-the-cat \
--to=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 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.