From: Hans de Goede <hdegoede@redhat.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH v5 0/3] ARM: Add armv7/Kconfig and allow booting in secure mode on non-secure boot capable systems
Date: Thu, 20 Nov 2014 15:34:19 +0100 [thread overview]
Message-ID: <546DFBEB.7090703@redhat.com> (raw)
In-Reply-To: <1415954071-5934-1-git-send-email-hdegoede@redhat.com>
Hi Albert,
On 11/14/2014 09:34 AM, Hans de Goede wrote:
> Hi Albert,
>
> Here is v5 of my patchset to allow booting in secure mode on non-secure boot
> capable systems.
>
> Changes in v2:
> -"ARM: Add arch/arm/cpu/armv7/Kconfig with non-secure and virt options":
> -Drop all the FIXME-s, use proper CPU_V7 and CPU_V7_HAS_foo checks instead
>
> Changes in v5:
> -Jump patch-set version to v5 to match the revision level of the patch
> with the highest revision in the set
> -"Kconfig: Add EXPERT option"
> -Add Masahiro Yamada's Acked-by
> -"ARM: Add arch/arm/cpu/armv7/Kconfig with non-secure and virt options":
> -Fix the commit message to refer to the right Kconfig option
> -"ARM: bootm: Allow booting in secure mode on hyp capable systems"
> -Fix ARMV7_BOOT_SEC_DEFAULT Kconfig help text mixing up secure and non-secure
> modes
I was wondering what the status of this patch-set is ?
Anything I need to do to get this moving upstream ?
Thanks & Regards,
Hans
prev parent reply other threads:[~2014-11-20 14:34 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-14 8:34 [U-Boot] [PATCH v5 0/3] ARM: Add armv7/Kconfig and allow booting in secure mode on non-secure boot capable systems Hans de Goede
2014-11-14 8:34 ` [U-Boot] [PATCH v5 1/3] Kconfig: Add EXPERT option Hans de Goede
2014-11-14 8:55 ` Albert ARIBAUD
2014-11-14 8:58 ` Hans de Goede
2014-11-20 15:43 ` Tom Rini
2014-11-21 9:18 ` Albert ARIBAUD
2014-11-14 8:34 ` [U-Boot] [PATCH v5 2/3] ARM: Add arch/arm/cpu/armv7/Kconfig with non-secure and virt options Hans de Goede
2014-11-14 8:34 ` [U-Boot] [PATCH v5 3/3] ARM: bootm: Allow booting in secure mode on hyp capable systems Hans de Goede
2014-11-20 14:34 ` Hans de Goede [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=546DFBEB.7090703@redhat.com \
--to=hdegoede@redhat.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.