All of lore.kernel.org
 help / color / mirror / Atom feed
From: Alexander Graf <agraf@suse.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] [U-Boot, v16, 3/4] efi: Create a function to set up for running EFI code
Date: Sat,  1 Dec 2018 00:21:39 +0100	[thread overview]
Message-ID: <154362009956.30674.9220353583447042072@achrid.arch.suse.de> (raw)
In-Reply-To: <20181126031439.202582-4-sjg@chromium.org>

> There is still duplicated code in efi_loader for tests and normal
> operation.
> 
> Add a new bootefi_run_prepare() function which holds common code used to
> set up U-Boot to run EFI code. Make use of this from the existing
> bootefi_test_prepare() function, as well as do_bootefi_exec().
> 
> Also shorten a few variable names.
> 
> Signed-off-by: Simon Glass <sjg@chromium.org>

Thanks, applied to efi-next

Alex

  reply	other threads:[~2018-11-30 23:21 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-11-26  3:14 [U-Boot] [PATCH v16 0/4] efi_loader: Code refactoring and improvement Simon Glass
2018-11-26  3:14 ` [U-Boot] [PATCH v16 1/4] efi: Check for failure to create objects in selftest Simon Glass
2018-11-30 23:21   ` [U-Boot] [U-Boot, v16, " Alexander Graf
2018-11-26  3:14 ` [U-Boot] [PATCH v16 2/4] efi: Split out test init/uninit into functions Simon Glass
2018-11-30 23:21   ` [U-Boot] [U-Boot, v16, " Alexander Graf
2018-11-26  3:14 ` [U-Boot] [PATCH v16 3/4] efi: Create a function to set up for running EFI code Simon Glass
2018-11-30 23:21   ` Alexander Graf [this message]
2018-11-26  3:14 ` [U-Boot] [PATCH v16 4/4] efi: Rename bootefi_test_finish() to bootefi_run_finish() Simon Glass
2018-11-30 23:21   ` [U-Boot] [U-Boot, v16, " Alexander Graf
2018-11-29 21:26 ` [U-Boot] [PATCH v16 0/4] efi_loader: Code refactoring and improvement Simon Glass
2018-11-30 21:27   ` Alexander Graf

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=154362009956.30674.9220353583447042072@achrid.arch.suse.de \
    --to=agraf@suse.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.