public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: Leif Lindholm <leif.lindholm@linaro.org>
To: Ard Biesheuvel <ard.biesheuvel@linaro.org>
Cc: "edk2-devel@lists.01.org" <edk2-devel@lists.01.org>
Subject: Re: [PATCH edk2-non-osi] Platform/DeveloperBox: add binary build of TF-A + standalone MM varstore
Date: Fri, 29 Mar 2019 10:06:49 +0000	[thread overview]
Message-ID: <20190329100649.o3fbllccvp4el33m@bivouac.eciton.net> (raw)
In-Reply-To: <CAKv+Gu_-RLidzYGK+Dd4DWV4_k8Q9Sb1hqsyt_r+T3mQie4xWQ@mail.gmail.com>

On Fri, Mar 29, 2019 at 10:52:41AM +0100, Ard Biesheuvel wrote:
> On Fri, 29 Mar 2019 at 09:57, Leif Lindholm <leif.lindholm@linaro.org> wrote:
> >
> > On Fri, Mar 29, 2019 at 08:46:12AM +0100, Ard Biesheuvel wrote:
> > > Provide a prebuilt binary of the standalone MM payload containing the
> > > UEFI authenticated variable store drivers. These are built from EDK2
> > > components, but the resulting image needs to be wrapped in a FIP
> > > container and built into the secure world TF-A image.
> > >
> > > TF-A commit:           e86e202c2e4e
> > > edk2 commit:           8028f0303218
> > > edk2-platforms commit: 05fdad573966
> > >
> > > Contributed-under: TianoCore Contribution Agreement 1.1
> > > Signed-off-by: Ard Biesheuvel <ard.biesheuvel@linaro.org>
> >
> > Reviewed-by: Leif Lindholm <leif.lindholm@linaro.org>
> >
> 
> Turns out I need to respin this based on 0a32c15d2172 (just pushed
> into edk2-platforms).

Right. Well, the reviewed-by stands, as long as the hash gets updated.

/
    Leif


  reply	other threads:[~2019-03-29 10:06 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-03-29  7:46 [PATCH edk2-non-osi] Platform/DeveloperBox: add binary build of TF-A + standalone MM varstore Ard Biesheuvel
2019-03-29  8:57 ` Leif Lindholm
2019-03-29  9:52   ` Ard Biesheuvel
2019-03-29 10:06     ` Leif Lindholm [this message]
2019-03-29 10:14       ` Ard Biesheuvel

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=20190329100649.o3fbllccvp4el33m@bivouac.eciton.net \
    --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