public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Tom Rini <trini@konsulko.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] Pull request for UEFI sub-system for efi-2020-01-rc1
Date: Mon, 7 Oct 2019 10:14:54 -0400	[thread overview]
Message-ID: <20191007141454.GA6716@bill-the-cat> (raw)
In-Reply-To: <c5765698-272d-8f77-ad68-7b11cabbdd3b@gmx.de>

On Sun, Oct 06, 2019 at 11:13:21PM +0200, Heinrich Schuchardt wrote:

> The following changes since commit dac51e9aaf6fd38298007b266feb6a80e9ec91ee:
> 
>   Merge branch 'master' of git://git.denx.de/u-boot-sh (2019-10-05
> 20:06:58 -0400)
> 
> are available in the Git repository at:
> 
>   https://gitlab.denx.de/u-boot/custodians/u-boot-efi.git
> tags/efi-2020-01-rc1
> 
> for you to fetch changes up to 3b728f8728fa7c596d30ecd27ebb64d37a54a12e:
> 
>   cmd: disable CMD_NVEDIT_EFI by default (2019-10-06 16:02:37 +0200)
> 
> ----------------------------------------------------------------
> Pull request for UEFI sub-system for efi-2020-01-rc1
> 
> The major corrections in this pull request are:
> 
> Fixes for the SetVariable() boot service.
> Device path node for NVMe drives.
> Disable CONFIG_CMD_NVEDIT by default.
> 
> Gitlab CI and Travis CI showed no problems:
> https://gitlab.denx.de/u-boot/custodians/u-boot-efi/pipelines/845
> https://travis-ci.org/xypron2/u-boot/builds/594214233
> 
> ----------------------------------------------------------------
> AKASHI Takahiro (1):
>       cmd: env: fix a typo in a comment of do_env_set_efi()
> 
> Heinrich Schuchardt (4):
>       efi_loader: appending to non-existent variable
>       efi_selftest: correct SetVariable() test
>       efi_selftest: testing read-only variables
>       cmd: disable CMD_NVEDIT_EFI by default
> 
> Mian Yousaf Kaukab (1):
>       Revert "ARM: tegra: reserve unmapped RAM so EFI doesn't use it"
> 
> Patrick Wildt (2):
>       nvme: add accessor to namespace id and eui64
>       efi: device path for nvme
> 
>  arch/arm/mach-tegra/board2.c              | 14 -----------
>  cmd/Kconfig                               |  1 -
>  cmd/nvedit_efi.c                          |  2 +-
>  drivers/nvme/nvme.c                       | 13 ++++++++++
>  drivers/nvme/nvme.h                       |  1 +
>  include/efi_api.h                         |  7 ++++++
>  include/nvme.h                            | 12 +++++++++
>  lib/efi_loader/efi_device_path.c          | 20 +++++++++++++++
>  lib/efi_loader/efi_device_path_to_text.c  | 15 +++++++++++
>  lib/efi_loader/efi_variable.c             | 10 +++++---
>  lib/efi_selftest/efi_selftest_variables.c | 41
> ++++++++++++-------------------
>  11 files changed, 91 insertions(+), 45 deletions(-)

Is this really release-day regression fix level of changes or can they
wait?  Thanks!

-- 
Tom
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: not available
URL: <http://lists.denx.de/pipermail/u-boot/attachments/20191007/e584ba15/attachment.sig>

  reply	other threads:[~2019-10-07 14:14 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-10-06 21:13 [U-Boot] Pull request for UEFI sub-system for efi-2020-01-rc1 Heinrich Schuchardt
2019-10-07 14:14 ` Tom Rini [this message]
2019-10-07 14:23   ` Bin Meng
2019-10-07 14:33     ` Tom Rini
2019-10-09 13:21 ` 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=20191007141454.GA6716@bill-the-cat \
    --to=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