public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: "Ard Biesheuvel" <ardb@kernel.org>
To: Etienne Carriere <etienne.carriere@linaro.org>
Cc: edk2-devel-groups-io <devel@edk2.groups.io>,
	Ard Biesheuvel <ardb+tianocore@kernel.org>,
	 Ilias Apalodimas <ilias.apalodimas@linaro.org>,
	Leif Lindholm <leif@nuviainc.com>,
	 Sami Mujawar <sami.mujawar@arm.com>,
	Sughosh Ganu <sughosh.ganu@linaro.org>,
	 Thomas Abraham <thomas.abraham@arm.com>
Subject: Re: [edk2-platforms][PATCH 0/4] Arm 32bit support in StandaloneMmRpmb
Date: Mon, 10 May 2021 17:57:08 +0200	[thread overview]
Message-ID: <CAMj1kXH0zdStJMvFSM9YN6WbZ4LkXnYYhg6e=d-Pb5wsMvTuvQ@mail.gmail.com> (raw)
In-Reply-To: <20210510075304.9125-1-etienne.carriere@linaro.org>

On Mon, 10 May 2021 at 09:53, Etienne Carriere
<etienne.carriere@linaro.org> wrote:
>
> This series brings support for building PlatformStandaloneMmRpmb for
> 32bit Arm architectures. This series is based on series [1] in edk2
> that allows to build StandaloneMm package for 32bit Arm. This series
> starts by syncing with paths changes from [1] series, then comes
> changes for Arm 32bit support in OpTee drivers and last updates
> PlatformStandaloneMmRpmb.dsc for 32bit the ARM architure.
>
> [1] https://edk2.groups.io/g/devel/message/74734
>
> Etienne Carriere (4):
>   sync with edk2 where StandaloneMmCpu moved to AArch64/ parent
>     directory
>   Drivers/OpTee: Add Aarch32 SVC IDs for 32bit Arm targets
>   Drivers/OpTee: address cast build warning issue in 32b mode
>   Platform/StandaloneMm: build StandaloneMmRpmb for 32bit architectures
>

This looks fine to me

Acked-by: Ard Biesheuvel <ardb@kernel.org>

I'll pick these up once the EDK2 side is merged.

>  Drivers/OpTee/OpteeRpmbPkg/OpTeeRpmbFvb.c     | 23 ++++++++++++-------
>  Drivers/OpTee/OpteeRpmbPkg/OpTeeRpmbFvb.h     | 16 +++++++++++--
>  Platform/ARM/SgiPkg/PlatformStandaloneMm.dsc  |  2 +-
>  Platform/ARM/SgiPkg/PlatformStandaloneMm.fdf  |  2 +-
>  .../Socionext/DeveloperBox/DeveloperBoxMm.dsc |  2 +-
>  .../Socionext/DeveloperBox/DeveloperBoxMm.fdf |  2 +-
>  .../PlatformStandaloneMmRpmb.dsc              | 14 +++++++++--
>  .../PlatformStandaloneMmRpmb.fdf              |  3 ++-
>  8 files changed, 47 insertions(+), 17 deletions(-)
>
> --
> 2.17.1
>

  parent reply	other threads:[~2021-05-10 15:57 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-10  7:53 [edk2-platforms][PATCH 0/4] Arm 32bit support in StandaloneMmRpmb Etienne Carriere
2021-05-10  7:53 ` [edk2-platforms][PATCH 1/4] sync with edk2 where StandaloneMmCpu moved to AArch64/ parent directory Etienne Carriere
2021-05-12 10:11   ` Sami Mujawar
2021-05-10  7:53 ` [edk2-platforms][PATCH 2/4] Drivers/OpTee: Add Aarch32 SVC IDs for 32bit Arm targets Etienne Carriere
2021-05-12 10:11   ` Sami Mujawar
2021-05-10  7:53 ` [edk2-platforms][PATCH 3/4] Drivers/OpTee: address cast build warning issue in 32b mode Etienne Carriere
2021-05-12 10:24   ` Sami Mujawar
2021-05-10  7:53 ` [edk2-platforms][PATCH 4/4] Platform/StandaloneMm: build StandaloneMmRpmb for 32bit architectures Etienne Carriere
2021-05-12 10:13   ` Sami Mujawar
2021-05-10 15:57 ` Ard Biesheuvel [this message]
2021-05-10 18:04   ` [edk2-platforms][PATCH 0/4] Arm 32bit support in StandaloneMmRpmb Ilias Apalodimas

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-list 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='CAMj1kXH0zdStJMvFSM9YN6WbZ4LkXnYYhg6e=d-Pb5wsMvTuvQ@mail.gmail.com' \
    --to=devel@edk2.groups.io \
    /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