From: Heinrich Schuchardt <xypron.glpk@gmx.de>
To: Tom Rini <trini@konsulko.com>
Cc: U-Boot Mailing List <u-boot@lists.denx.de>,
Alexander Graf <agraf@csgraf.de>,
Masahisa Kojima <masahisa.kojima@linaro.org>,
Ilias Apalodimas <ilias.apalodimas@linaro.org>,
AKASHI Takahiro <takahiro.akashi@linaro.org>
Subject: Pull request for efi-2021-10-rc4
Date: Sat, 4 Sep 2021 11:56:47 +0200 [thread overview]
Message-ID: <61e2e1cc-b474-84dd-eceb-bb86a59972be@gmx.de> (raw)
Dear Tom,
The following changes since commit 94509b79b13e69c209199af0757afbde8d2ebd6d:
btrfs: Use default subvolume as filesystem root (2021-09-01 10:11:24
-0400)
are available in the Git repository at:
https://source.denx.de/u-boot/custodians/u-boot-efi.git
tags/efi-2021-10-rc4
for you to fetch changes up to 1dfa494610c5469cc28cf1f8538abf4be6c00324:
efi_loader: fix efi_tcg2_hash_log_extend_event() parameter check
(2021-09-04 09:15:09 +0200)
----------------------------------------------------------------
Pull request for efi-2021-10-rc4
Documentation:
Remove invalid reference to configuration variable in UEFI doc
UEFI:
Parameter checks for the EFI_TCG2_PROTOCOL
Improve support of preseeding UEFI variables.
Correct the calculation of the size of loaded images.
Allow for UEFI images with zero VirtualSize
----------------------------------------------------------------
Heinrich Schuchardt (5):
efi_loader: sections with zero VirtualSize
efi_loader: rounding of image size
efi_loader: don't load signature database from file
efi_loader: efi_auth_var_type for AuditMode, DeployedMode
efi_loader: correct determination of secure boot state
Masahisa Kojima (3):
efi_loader: add missing parameter check for EFI_TCG2_PROTOCOL api
efi_loader: fix boot_service_capability_min calculation
efi_loader: fix efi_tcg2_hash_log_extend_event() parameter check
include/efi_tcg2.h | 4 +++-
include/efi_variable.h | 6 +++++-
lib/efi_loader/efi_image_loader.c | 35 +++++++++++++++++++++++++------
lib/efi_loader/efi_tcg2.c | 21 ++++++++++++++++++-
lib/efi_loader/efi_var_common.c | 43
++++++++++++++++++++++++++++++---------
lib/efi_loader/efi_var_file.c | 41
++++++++++++++++++++++---------------
lib/efi_loader/efi_variable.c | 6 +++---
7 files changed, 118 insertions(+), 38 deletions(-)
next reply other threads:[~2021-09-04 9:57 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-04 9:56 Heinrich Schuchardt [this message]
2021-09-04 10:10 ` Pull request for efi-2021-10-rc4 Heinrich Schuchardt
2021-09-06 14:31 ` Tom Rini
2021-09-04 13:01 ` Tom Rini
2021-09-04 13:08 ` Heinrich Schuchardt
2021-09-04 13:19 ` Tom Rini
2021-09-04 14:37 ` Tom Rini
2021-09-04 17:03 ` Heinrich Schuchardt
2021-09-04 17:39 ` Tom Rini
2021-09-04 18:02 ` Heinrich Schuchardt
2021-09-04 18:08 ` Tom Rini
2021-09-04 20:08 ` Ilias Apalodimas
2021-09-06 0:47 ` AKASHI Takahiro
2021-09-09 8:56 ` Simon Glass
2021-09-09 11:21 ` Heinrich Schuchardt
2021-09-09 12:01 ` Tom Rini
2021-09-09 8:56 ` Simon Glass
2021-09-09 10:52 ` Heinrich Schuchardt
2021-09-09 12:08 ` Tom Rini
2021-09-09 20:08 ` Simon Glass
2021-09-09 20:44 ` Tom Rini
2021-09-09 21:22 ` Mark Kettenis
2021-09-10 10:28 ` François Ozog
2021-09-09 12:17 ` François Ozog
2021-09-09 20:08 ` Simon Glass
2021-09-10 10:40 ` François Ozog
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=61e2e1cc-b474-84dd-eceb-bb86a59972be@gmx.de \
--to=xypron.glpk@gmx.de \
--cc=agraf@csgraf.de \
--cc=ilias.apalodimas@linaro.org \
--cc=masahisa.kojima@linaro.org \
--cc=takahiro.akashi@linaro.org \
--cc=trini@konsulko.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox