From: "Ard Biesheuvel" <ard.biesheuvel@linaro.org>
To: Pete Batard <pete@akeo.ie>
Cc: edk2-devel-groups-io <devel@edk2.groups.io>,
"Leif Lindholm" <leif.lindholm@linaro.org>,
"Philippe Mathieu-Daudé" <philmd@redhat.com>,
samer.el-haj-mahmoud@arm.com,
"Andrei E. Warkentin" <andrey.warkentin@gmail.com>
Subject: Re: [edk2-platforms][PATCH v2 0/3] Further RPi4 support groundwork
Date: Mon, 2 Dec 2019 17:43:50 +0000 [thread overview]
Message-ID: <CAKv+Gu_rWQ6hQvrFA1uDziMZ6towm-nCJ4TTeCuNpJN6FzdfJQ@mail.gmail.com> (raw)
In-Reply-To: <20191202171622.10980-1-pete@akeo.ie>
On Mon, 2 Dec 2019 at 17:16, Pete Batard <pete@akeo.ie> wrote:
>
> Changes from v1 (https://edk2.groups.io/g/devel/message/51334):
> - Moved RNG related changes into their own series
> - Fix a whitespace issue in the last patch
>
> Andrei Warkentin (2):
> Platform/RPi/MmcDxe: Factorize SCR call and clean up MMC init
> Platform/RPi/MmcDxe: Improve MMC driver stability
>
> Samer El-Haj-Mahmoud (1):
> Platform/RPi: Set SD routing according to model
>
Reviewed-by: Ard Biesheuvel <ard.biesheuvel@linaro.org>
Pushed as d6b7f67e62da..0e6e3fc4af67
Thanks,
> Platform/RaspberryPi/Drivers/ConfigDxe/ConfigDxe.c | 137 ++++++++++++++------
> Platform/RaspberryPi/Drivers/MmcDxe/Mmc.c | 7 +-
> Platform/RaspberryPi/Drivers/MmcDxe/MmcIdentification.c | 105 +++++++++------
> 3 files changed, 164 insertions(+), 85 deletions(-)
>
> --
> 2.21.0.windows.1
>
prev parent reply other threads:[~2019-12-02 17:43 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-02 17:16 [edk2-platforms][PATCH v2 0/3] Further RPi4 support groundwork Pete Batard
2019-12-02 17:16 ` [edk2-platforms][PATCH v2 1/3] Platform/RPi/MmcDxe: Factorize SCR call and clean up MMC init Pete Batard
2019-12-02 17:16 ` [edk2-platforms][PATCH v2 2/3] Platform/RPi/MmcDxe: Improve MMC driver stability Pete Batard
2019-12-02 17:16 ` [edk2-platforms][PATCH v2 3/3] Platform/RPi: Set SD routing according to model Pete Batard
2019-12-02 17:43 ` 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=CAKv+Gu_rWQ6hQvrFA1uDziMZ6towm-nCJ4TTeCuNpJN6FzdfJQ@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