From: Tom Rini <trini@konsulko.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] mach-omap2: Fix secure boot media generation
Date: Fri, 20 Jan 2017 22:37:51 -0500 [thread overview]
Message-ID: <20170121033751.GW25981@bill-the-cat> (raw)
In-Reply-To: <20170112162158.14923-1-afd@ti.com>
On Thu, Jan 12, 2017 at 10:21:58AM -0600, Andrew F. Davis wrote:
> While moving OMAP related files to mach-omap2 the functionality
> relating to generating secure boot files was modified. This change
> prevents secure platforms other than AM33xx and OMAP54XX from
> correctly building files for all needed media types.
>
> Fixes: 983e37007da5 ("arm: Introduce arch/arm/mach-omap2 for OMAP2 derivative platforms")
> Signed-off-by: Andrew F. Davis <afd@ti.com>
> Acked-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: 819 bytes
Desc: Digital signature
URL: <http://lists.denx.de/pipermail/u-boot/attachments/20170120/6f2a3394/attachment.sig>
prev parent reply other threads:[~2017-01-21 3:37 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-12 16:21 [U-Boot] [PATCH] mach-omap2: Fix secure boot media generation Andrew F. Davis
2017-01-13 3:29 ` Lokesh Vutla
2017-01-21 3:37 ` Tom Rini [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=20170121033751.GW25981@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