From: Tom Rini <trini@konsulko.com>
To: u-boot@lists.denx.de
Subject: [PATCH 1/1] config: remove CONFIG_ARMV8_SWITCH_TO_EL1 from whitelist.txt
Date: Tue, 2 Jun 2020 16:07:15 -0400 [thread overview]
Message-ID: <20200602200715.GV21630@bill-the-cat> (raw)
In-Reply-To: <20200602194556.6741-1-xypron.glpk@gmx.de>
On Tue, Jun 02, 2020 at 09:45:56PM +0200, Heinrich Schuchardt wrote:
> Since commit 208bdaf2ae5f ("vexpress/aemv8a: drop
> CONFIG_ARMV8_SWITCH_TO_EL1") no board uses CONFIG_ARMV8_SWITCH_TO_EL1. So
> we should remove this setting from whitelist.txt. If anybody should ever
> need it again, he should add a Kconfig option.
>
> Signed-off-by: Heinrich Schuchardt <xypron.glpk@gmx.de>
> ---
> scripts/config_whitelist.txt | 1 -
> 1 file changed, 1 deletion(-)
>
> diff --git a/scripts/config_whitelist.txt b/scripts/config_whitelist.txt
> index fe9a1971cc..15b77c981e 100644
> --- a/scripts/config_whitelist.txt
> +++ b/scripts/config_whitelist.txt
> @@ -49,7 +49,6 @@ CONFIG_ARMV7_PSCI_1_0
> CONFIG_ARMV7_SECURE_BASE
> CONFIG_ARMV7_SECURE_MAX_SIZE
> CONFIG_ARMV7_SECURE_RESERVE_SIZE
> -CONFIG_ARMV8_SWITCH_TO_EL1
> CONFIG_ARM_ARCH_CP15_ERRATA
> CONFIG_ARM_DCC
> CONFIG_ARM_FREQ
Nak, the file is auto-generated. That said, scripts/build-whitelist.sh
might be able to note that up top without breaking the logic used to
break builds that add new symbols.
The next problem however is that the code around
CONFIG_ARMV8_SWITCH_TO_EL1 hasn't been removed, and needs to be
otherwise the symbol will be listed again when I run the generator next.
Thanks!
--
Tom
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 659 bytes
Desc: not available
URL: <https://lists.denx.de/pipermail/u-boot/attachments/20200602/a2c1e6a4/attachment.sig>
prev parent reply other threads:[~2020-06-02 20:07 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-02 19:45 [PATCH 1/1] config: remove CONFIG_ARMV8_SWITCH_TO_EL1 from whitelist.txt Heinrich Schuchardt
2020-06-02 20:07 ` Tom Rini [this message]
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=20200602200715.GV21630@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