From: Heinrich Schuchardt <xypron.glpk@gmx.de>
To: u-boot@lists.denx.de
Subject: Pull request for UEFI sub-system for efi-2020-10-rc5 (2)
Date: Sat, 19 Sep 2020 07:24:22 +0200 [thread overview]
Message-ID: <d42be5b6-6a9f-ef64-c11d-b37104c7056f@gmx.de> (raw)
Hello Tom,
The following changes since commit 9de3126e80cdac7ee15b6671065a952184533dda:
Merge branch '2020-09-16-assorted-fixes' (2020-09-17 09:53:57 -0400)
are available in the Git repository at:
https://gitlab.denx.de/u-boot/custodians/u-boot-efi.git
tags/efi-2020-10-rc5-2
for you to fetch changes up to 8f0ac536d4937d07a95fcc56756c14ef7a94e397:
efi: change 'env -e -i' usage syntax (2020-09-18 22:23:58 +0200)
Gitlab CI and Travis CI showed no problems:
https://gitlab.denx.de/u-boot/custodians/u-boot-efi/-/pipelines/4709
https://travis-ci.org/github/xypron2/u-boot/builds/728440733
----------------------------------------------------------------
Pull request for UEFI sub-system for efi-2020-10-rc5 (2)
The following bugs are fixed:
* incorrect online help for setenv and env
* description of function efi_mem_carve_out()
* replace printf() by log_err() in stm32mp1_rng driver
A unit test is provided to check that the boot hart id is available in
the RISC-V device-tree.
----------------------------------------------------------------
Heinrich Schuchardt (3):
rng: stm32mp1: use log() instead of printf()
efi_selftest: rework device tree test
efi_selftest: check for RISC-V boot-hartid in FDT
Maxim Uvarov (2):
efi_memory: refine overlap_only_ram description
efi: change 'env -e -i' usage syntax
cmd/nvedit.c | 4 +--
drivers/rng/stm32mp1_rng.c | 4 ++-
lib/efi_loader/efi_memory.c | 2 +-
lib/efi_selftest/efi_selftest_fdt.c | 68
+++++++++++++++++++++++++++++--------
4 files changed, 60 insertions(+), 18 deletions(-)
next reply other threads:[~2020-09-19 5:24 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-19 5:24 Heinrich Schuchardt [this message]
2020-09-20 13:53 ` Pull request for UEFI sub-system for efi-2020-10-rc5 (2) Tom Rini
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=d42be5b6-6a9f-ef64-c11d-b37104c7056f@gmx.de \
--to=xypron.glpk@gmx.de \
--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.