diff options
author | Rasmus Villemoes <rasmus.villemoes@prevas.dk> | 2022-10-28 13:50:51 +0200 |
---|---|---|
committer | Stefan Roese <sr@denx.de> | 2022-11-02 08:41:42 +0100 |
commit | 6b84b1db2d69609a783ab2fd6990c9e72903d367 (patch) | |
tree | 6be338c661d689c9cb1b7e64dd046b283785a0e0 /include/keys | |
parent | d7de5ef629352fe12ad99b6539ba1480b923f31e (diff) | |
download | u-boot-6b84b1db2d69609a783ab2fd6990c9e72903d367.tar.gz u-boot-6b84b1db2d69609a783ab2fd6990c9e72903d367.tar.bz2 u-boot-6b84b1db2d69609a783ab2fd6990c9e72903d367.zip |
cyclic: drop redundant cyclic_ready flag
We're already relying on gd->cyclic being NULL before cyclic_init() is
called - i.e., we're relying on all of gd being zeroed before entering
any C code. And when we do populate gd->cyclic, its ->cyclic_ready
member is automatically set to true. So we can actually just rely on
testing gd->cyclic itself.
The only wrinkle is that cyclic_uninit() actually did set
->cyclic_ready to false. However, since it doesn't free gd->cyclic,
the cyclic infrastructure is actually still ready (i.e., the list_head
is properly initialized as an empty list).
Signed-off-by: Rasmus Villemoes <rasmus.villemoes@prevas.dk>
Reviewed-by: Stefan Roese <sr@denx.de>
Tested-by: Stefan Roese <sr@denx.de>
Tested-by: Tim Harvey <tharvey@gateworks.com> # imx8mm-venice-*
Diffstat (limited to 'include/keys')
0 files changed, 0 insertions, 0 deletions