From: Tom Rini <trini@ti.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH 1/2] ARM: Add arch/arm/cpu/armv7/Kconfig with non-secure and virt options
Date: Sun, 26 Oct 2014 20:35:59 -0400 [thread overview]
Message-ID: <20141027003559.GR25506@bill-the-cat> (raw)
In-Reply-To: <1414175656-14491-2-git-send-email-hdegoede@redhat.com>
On Fri, Oct 24, 2014 at 08:34:15PM +0200, Hans de Goede wrote:
> Add arch/arm/cpu/armv7/Kconfig with non-secure and virt options, so that
> we can have CONFIG_ARMV7_SEC_BY_DEFAULT as a proper Kconfig option.
>
> Signed-off-by: Hans de Goede <hdegoede@redhat.com>
> ---
> arch/arm/Kconfig | 2 ++
> arch/arm/cpu/armv7/Kconfig | 20 ++++++++++++++++++++
> include/configs/arndale.h | 2 --
> include/configs/sun7i.h | 2 --
> include/configs/vexpress_ca15_tc2.h | 2 --
The only problem I see is you aren't also updating the defconfigs for
the boards in question, which results in a behavior change which we
don't want.
--
Tom
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 836 bytes
Desc: Digital signature
URL: <http://lists.denx.de/pipermail/u-boot/attachments/20141026/adbba8bb/attachment.pgp>
next prev parent reply other threads:[~2014-10-27 0:35 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-24 18:34 [U-Boot] [PATCH v4 0/2] ARM: Add non-secure / virt Kconfig options and allow secure boot on non-secure configs Hans de Goede
2014-10-24 18:34 ` [U-Boot] [PATCH 1/2] ARM: Add arch/arm/cpu/armv7/Kconfig with non-secure and virt options Hans de Goede
2014-10-27 0:35 ` Tom Rini [this message]
2014-10-27 8:48 ` Hans de Goede
2014-10-27 9:24 ` Ian Campbell
2014-10-24 18:34 ` [U-Boot] [PATCH 2/2] ARM: bootm: Allow booting in secure mode on hyp capable systems Hans de Goede
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=20141027003559.GR25506@bill-the-cat \
--to=trini@ti.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