From: Tom Rini <trini@konsulko.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH v4 2/6] spl: Add option to enable SPL Legacy image support
Date: Tue, 14 Feb 2017 15:16:01 -0500 [thread overview]
Message-ID: <20170214201601.GP26129@bill-the-cat> (raw)
In-Reply-To: <20170213184741.8755-3-afd@ti.com>
On Mon, Feb 13, 2017 at 12:47:37PM -0600, Andrew F. Davis wrote:
> Add a Kconfig option that enables Legacy image support, this allows
> boards to explicitly disable this, for instance when needed for
> security reasons.
>
> Signed-off-by: Andrew F. Davis <afd@ti.com>
> Reviewed-by: Simon Glass <sjg@chromium.org>
Reviewed-by: Tom Rini <trini@konsulko.com>
--
Tom
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: Digital signature
URL: <http://lists.denx.de/pipermail/u-boot/attachments/20170214/f034e981/attachment.sig>
next prev parent reply other threads:[~2017-02-14 20:16 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-13 18:47 [U-Boot] [PATCH v4 0/6] Allow disabling non-FIT image loading from SPL Andrew F. Davis
2017-02-13 18:47 ` [U-Boot] [PATCH v4 1/6] spl: Convert CONFIG_SPL_ABORT_ON_RAW_IMAGE into a positive option Andrew F. Davis
2017-02-14 20:15 ` Tom Rini
2017-02-14 20:32 ` Andrew F. Davis
2017-02-14 21:04 ` Tom Rini
2017-02-15 19:37 ` Andrew F. Davis
2017-02-13 18:47 ` [U-Boot] [PATCH v4 2/6] spl: Add option to enable SPL Legacy image support Andrew F. Davis
2017-02-14 20:16 ` Tom Rini [this message]
2017-02-13 18:47 ` [U-Boot] [PATCH v4 3/6] ARM: AM335x: Disable non-FIT based image loading for HS devices Andrew F. Davis
2017-02-14 20:16 ` Tom Rini
2017-02-13 18:47 ` [U-Boot] [PATCH v4 4/6] ARM: AM43xx: " Andrew F. Davis
2017-02-14 20:16 ` Tom Rini
2017-02-13 18:47 ` [U-Boot] [PATCH v4 5/6] ARM: AM57xx: " Andrew F. Davis
2017-02-14 20:17 ` Tom Rini
2017-02-13 18:47 ` [U-Boot] [PATCH v4 6/6] ARM: DRA7xx: " Andrew F. Davis
2017-02-14 20:17 ` 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=20170214201601.GP26129@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