From: Alexander Graf <agraf@suse.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH v12 2/6] efi_loader: Drop setup_ok
Date: Tue, 13 Nov 2018 20:59:34 +0100 [thread overview]
Message-ID: <04ae8d4e-d06d-e0f0-a005-6853a8aeb429@suse.de> (raw)
In-Reply-To: <20181106225744.139945-3-sjg@chromium.org>
On 06.11.18 23:57, Simon Glass wrote:
> This value is stored in data which appears to be read-only with sandbox on
> my Ubuntu 18.04 machine. In any case it is not good practice to store
> run-time data in a build-time linker list.
>
> The value does not seem to be that useful, since tests that fail to setup
> are likely to fail to run also. Let's drop it for now.
>
> Signed-off-by: Simon Glass <sjg@chromium.org>
I think I already have this as "efi_selftest: do not write to linker
generated array" in my queue?
Alex
next prev parent reply other threads:[~2018-11-13 19:59 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-06 22:57 [U-Boot] [PATCH v12 0/6] efi_loader: Code refactoring and improvement Simon Glass
2018-11-06 22:57 ` [U-Boot] [PATCH v12 1/6] sandbox: Put CPUs under a cpu-bus node Simon Glass
2018-11-13 22:23 ` [U-Boot] [U-Boot, v12, " Alexander Graf
2018-11-14 8:34 ` [U-Boot] [PATCH v12 " Alexander Graf
2018-11-15 20:01 ` Simon Glass
2018-11-15 20:05 ` Alexander Graf
2018-11-06 22:57 ` [U-Boot] [PATCH v12 2/6] efi_loader: Drop setup_ok Simon Glass
2018-11-13 19:59 ` Alexander Graf [this message]
2018-11-13 21:35 ` Simon Glass
2018-11-06 22:57 ` [U-Boot] [PATCH v12 3/6] sandbox: smbios: Update to support sandbox Simon Glass
2018-11-13 20:03 ` Alexander Graf
2018-11-06 22:57 ` [U-Boot] [PATCH v12 4/6] efi: Split out test init/uninit into functions Simon Glass
2018-11-13 20:16 ` Alexander Graf
2018-11-06 22:57 ` [U-Boot] [PATCH v12 5/6] efi: Create a function to set up for running EFI code Simon Glass
2018-11-13 20:21 ` Alexander Graf
2018-11-06 22:57 ` [U-Boot] [PATCH v12 6/6] efi: Rename bootefi_test_finish() to bootefi_run_finish() Simon Glass
2018-11-13 19:53 ` [U-Boot] [PATCH v12 0/6] efi_loader: Code refactoring and improvement Simon Glass
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=04ae8d4e-d06d-e0f0-a005-6853a8aeb429@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox