From: "Ard Biesheuvel" <ard.biesheuvel@arm.com>
To: Samer El-Haj-Mahmoud <Samer.El-Haj-Mahmoud@arm.com>,
devel@edk2.groups.io
Cc: Leif Lindholm <leif@nuviainc.com>, Pete Batard <pete@akeo.ie>,
Andrei Warkentin <awarkentin@vmware.com>
Subject: Re: [edk2-platform][PATCH v1 0/2] Platforms/RaspberryPi: Fix RngLib build error
Date: Sun, 27 Sep 2020 11:57:33 +0200 [thread overview]
Message-ID: <2fcc8628-a483-15e8-d345-b2e25da29f4e@arm.com> (raw)
In-Reply-To: <20200926145230.5332-1-Samer.El-Haj-Mahmoud@arm.com>
On 9/26/20 4:52 PM, Samer El-Haj-Mahmoud wrote:
> Commit b5701a4c7a0fb185e0c5b9db9525939c78664bfd introduced RngLib
> dependency for OpensslLib, and caused the RPi build to break for lack
> of an RngLib instance.
>
> This series adds RngLib to both RPi3 and RPi4 using the DxeRngLib flavor,
> which is a wrapper around the the EFI_RNG_PROTOCOL that the platform
> already produces.
>
> Cc: Leif Lindholm <leif@nuviainc.com>
> Cc: Ard Biesheuvel <ard.biesheuvel@arm.com>
> Cc: Pete Batard <pete@akeo.ie>
> Cc: Andrei Warkentin <awarkentin@vmware.com>
> Signed-off-by: Samer El-Haj-Mahmoud <samer.el-haj-mahmoud@arm.com>
>
> Samer El-Haj-Mahmoud (2):
> Platforms/RaspberryPi: Fix RPi4 RngLib build error
> Platforms/RaspberryPi: Fix RPi3 RngLib build error
>
Pushed as 4efd9ab2cfab..1e09147a01ae
Thanks all,
prev parent reply other threads:[~2020-09-27 9:57 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-26 14:52 [edk2-platform][PATCH v1 0/2] Platforms/RaspberryPi: Fix RngLib build error Samer El-Haj-Mahmoud
2020-09-26 14:52 ` [edk2-platform][PATCH v1 1/2] Platforms/RaspberryPi: Fix RPi4 " Samer El-Haj-Mahmoud
2020-09-27 3:58 ` Andrei Warkentin
2020-09-26 14:52 ` [edk2-platform][PATCH v1 2/2] Platforms/RaspberryPi: Fix RPi3 " Samer El-Haj-Mahmoud
2020-09-27 3:58 ` Andrei Warkentin
2020-09-27 9:57 ` Ard Biesheuvel [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-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=2fcc8628-a483-15e8-d345-b2e25da29f4e@arm.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