From: Tom Rini <trini@konsulko.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH 2/3] tools: fit_image: Use fit_image_get_data_and_size for getting offset/size
Date: Wed, 8 Jan 2020 15:10:28 -0500 [thread overview]
Message-ID: <20200108201028.GO31026@bill-the-cat> (raw)
In-Reply-To: <20190917210935.3666-2-afd@ti.com>
On Tue, Sep 17, 2019 at 05:09:34PM -0400, Andrew F. Davis wrote:
> This is very similar to fit_image_get_data but has the benefit of working
> on FIT images with external data unlike fit_image_get_data. This is
> useful for extracting sub-images from type of FIT image as this would
> previously just silently fail. Add an error message also so if this
> still fails it is easier to find out why.
>
> Signed-off-by: Andrew F. Davis <afd@ti.com>
> Reviewed-by: Lokesh Vutla <lokeshvutla@ti.com>
Applied to u-boot/master, thanks!
--
Tom
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: not available
URL: <https://lists.denx.de/pipermail/u-boot/attachments/20200108/9fe6b88c/attachment.sig>
next prev parent reply other threads:[~2020-01-08 20:10 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-17 21:09 [U-Boot] [PATCH 1/3] tools: dumpimage: Provide more feedback on internal errors Andrew F. Davis
2019-09-17 21:09 ` [U-Boot] [PATCH 2/3] tools: fit_image: Use fit_image_get_data_and_size for getting offset/size Andrew F. Davis
2019-11-14 11:46 ` Lokesh Vutla
2020-01-08 20:10 ` Tom Rini [this message]
2019-09-17 21:09 ` [U-Boot] [PATCH 3/3] tools: dumpimage: Fall-though to print usage for help command Andrew F. Davis
2019-11-14 11:46 ` Lokesh Vutla
2020-01-08 20:10 ` Tom Rini
2019-11-13 16:14 ` [U-Boot] [PATCH 1/3] tools: dumpimage: Provide more feedback on internal errors Andrew F. Davis
2020-01-07 14:07 ` Andrew F. Davis
2019-11-14 11:46 ` Lokesh Vutla
2020-01-08 20:10 ` 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=20200108201028.GO31026@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox